home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Mac Magazin/MacEasy 12
/
Mac Magazin and MacEasy Magazine CD - Issue 12.iso
/
Sharewarebibliothek
/
DFÜ
/
Internet
/
faq
< prev
next >
Wrap
Text File
|
1995-07-25
|
191KB
|
3,971 lines
Last-modified: Sun Jun 25 1995
This is the Frequently Asked Questions (FAQ) list for comp.sys.mac.comm
=======================================================================
This list of frequently asked questions and answers is intended to help
reduce the number of "often asked questions" that make the rounds here
in comp.sys.mac.comm. Since comp.sys.mac.comm is intended as a forum to
discuss telecommunication (and related issues) that are specific to the
Macintosh, most questions about modems, telecommunications in general,
and other non-Macintosh specific communication questions are not listed
here. The proper newsgroup for such questions is usually comp.dcom.modems.
This list is posted periodically (about once a month) to the Usenet
groups comp.sys.mac.comm, news.answers, and comp.answers. Latest versions
of the FAQ can be retrieved via anonymous FTP from the following sites:
file://mac.archive.umich.edu/mac/misc/documentation/compsysmaccommfaq.txt
file://sumex-aim.stanford.edu/info-mac/comm/info/comp-sys-mac-comm-faq.txt
file://rtfm.mit.edu/pub/usenet/comp.sys.mac.comm/c.s.m.c_FAQ_[1_4]
c.s.m.c_FAQ_[2_4]
c.s.m.c_FAQ_[3_4]
c.s.m.c_FAQ_[4_4]
It also available in the Macintosh SIG on Delphi for Delphi members.
This FAQ is purely a volunteer effort. Although every effort has been
made to insure that answers are as complete and accurate as possible,
NO GUARANTEE IS IMPLIED OR INTENDED. The editor and contributors have
developed this FAQ as a service to Usenet. We hope you find it useful.
It has been formatted in setext format for your browsing convenience;
use a setext browser, such as EasyView, to take advantage of setext.
Please send your corrections and comments to the editor, David Oppenheimer,
at csmc-faq@phoenix.Princeton.EDU.
SHARE THIS INFORMATION FREELY AND IN GOOD FAITH.
DO NOT DISTRIBUTE MODIFIED VERSIONS OF THIS FAQ.
DO NOT REMOVE THIS NOTICE OR THE TEXT ABOVE.
(INCLUDING THE 'LastModified' HEADER; THANKS.)
Exception to the above: Excerpts of this FAQ not exceeding 9000 characters
in length may be reprinted PROVIDED that "the comp.sys.mac.comm Usenet
newsgroup FAQ" is credited as the source of the information. Even in this
case, no editing of the quoted material is permitted. If you have any
questions about the reprint policy, send mail to csmc-faq@phoenix.Princeton.EDU.
================================================================================
**** TABLE OF CONTENTS: ****
[1] Modems and Cables
[1.1] What kind of modem will work with my Macintosh?
[1.2] What kind of cable do I need to use my external modem with my
Macintosh? (Includes cable pinouts)
[1.3] What do V.32, V.42, bis, MNP, etc mean?
[1.4] How fast can the Macintosh serial ports really go?
[1.5] How can I disable call-waiting when using my modem?
[2] File Formats and Conversion
[2.1] What is a resource (or data) fork?
[2.2] What is MacBinary?
[2.3] What is BinHex? What is uuencode? What are atob/btoa ?
[2.4] What is Apple-Single/Double ?
[2.5] What do file suffixes like .hqx, .sit, .bin, etc ... mean
and how can I convert such files back to normal Macintosh
applications and documents?
[2.6] How can I use a binary-downloaded file that appears as an
unusable text file on the Mac desktop?
[3] Macintosh File Transfers
[3.1] What program(s) do(es) Kermit, FTP (client), and/or
X,Y,Z-MODEM and where can I get them?
[3.2] What is the latest version of ZTerm? How can I find out more
about ZTerm?
[3.3] What is the Communications Toolbox (CTB)?
[3.4] Are there any public-domain or shareware Communication
Toolbox tools that support Kermit, and/or X,Y,Z-MODEM?
[3.5] How can I transfer Macintosh files to/from my Macintosh and
other non-Macintosh computers (eg: mainframes, UNIX boxes,
PCs)?
[3.6] What's the best compression program to use when uploading
files to an archive or BBS? Are there any other guidelines
I should follow?
[3.7] How can I use the programs that are posted to
comp.binaries.mac?
[4] Introduction to AppleTalk (and Apple Remote Access)
[4.1] What kind of hardware do I need to set up an LocalTalk
network?
[4.2] How can I change the Chooser "user" and name of my
Macintosh? Also: Why can I no longer change the name of
my hard-disk?
[4.3] What is Apple Remote Access?
[4.4] Where can I get a Remote Access script for my modem?
[4.5] How are IP packets transmitted over a LocalTalk network?
[4.6] How can I use Apple Remote Access to access the Internet via my
Mac at work?
[4.7] How can I use the services of my EtherTalk network and print
to my LocalTalk-only printer at the same time?
[4.8] Is it possible to use AppleTalk over a TCP/IP network?
[5] TCP/IP Networking, MacTCP, Telnet, SLIP, PPP
[5.1] What is MacTCP and what kind of hardware and software do I
need to use it?
[5.2] What is the difference between AppleTalk, LocalTalk,
Ethernet, EtherTalk, TCP/IP, etc?
[5.3] What is Telnet, and is there a Telnet program for the
Macintosh?
[5.4] Is there a FTP (client/server) program for the Macintosh?
[5.5] What are SLIP, CSLIP and PPP?
[5.6] What is the difference between SLIP and PPP?
[5.7] MacPPP Frequently Asked Questions
[5.8] How does MacTCP resolve names into IP addresses?
[5.9] Is there a version of traceroute available for the Mac?
[5.10] What Domain Name Server programs are available for the Mac?
[6] MacX and Other Ways to Interface With UNIX
[6.1] Can I run X-Windows on my Mac?
[6.2] How can I run MacX over a modem? Is it feasible?
[6.3] What is MacLayers and what do I need to use it?
[6.4] What are UW and MultiSession? Are there other programs like
MacLayers?
[6.5] Is there a UNIX program that will convert between BinHex and
MacBinary?
[6.6] How can I create LaserWriter PostScript printer files and
print them on a PostScript printer connected to a UNIX
network?
[6.7] How can I print over the network to a QuickDraw printer which
doesn't support PostScript but is connected to a Macintosh?
[6.8] What is the Columbia AppleTalk Package (CAP)?
[6.9] How can I use the UNIX NFS file sharing protocol on my Mac?
[7] Sending and receiving mail and USENET news with your Macintosh
[7.1] How can I send/receive Internet mail with my Macintosh?
[7.2] How can I read/post Usenet news with my Macintosh?
[8] Miscellaneous
[8.1] I don't have FTP --- How can I access the various archives
through e-mail?
[8.2] What aids are available for programmers wishing to write TCP/IP
applications for the Macintosh?
[8.3] I have a FAX machine and a FAX modem. How can I use these
devices together to emulate a scanner and a printer?
Appendices:
[A] List of Common File Suffixes and Abbreviations
[B] List of Macintosh archive sites available through the Internet
[C] Vendor Information
[D] Contributors
================================================================================
[1] Modems and Cables
=====================
[1.1] What kind of modem will work with my Macintosh?
-----------------------------------------------------
Any *external* Hayes compatible modem will work with your
Macintosh. There are too many to list or review here. The
USENET newsgroup comp.dcom.modems is a good place to ask questions
about the many different external Hayes compatible modems. Such
modems can be used with any computer (Macintosh, UNIX box,
MS-DOS PC, Amiga, etc) with a serial port (e.g.: Macintosh modem
port) interface. However, there *are* modems that are designed
specifically for use with the Macintosh. Internal Powerbook
modems, ADB modems, and internal NuBus modems are all examples.
Note that modems for the Macintosh Performa apparently can only
plug into the Macintosh Performa because of an extra pin which
they posesses (there is a corresponding extra hole on the Performa
serial port connector into which this pin fits). As a result,
the bundled Global Village FAX modem can only plug into the Performa.
Other modems can of course also plug into the Performa; the extra
pin only prevents plugging the Performa-specific modem into other
Macs.
Assuming you wish to use an external modem, your only other
hardware consideration is to find an appropriate cable to connect
it to your Macintosh. Especially at higher bps rates (9600 bps
and up), a hardware-handshaking cable is recommended (see [1.2]
for details). There are many non-hardware-handshaking cables
being sold at reputable computer accessory stores, so it's
recommended that you ask before buying.
Various special modems exist with unique features; the most
notable type is the dual FAX/modem. For more information,
visit comp.dcom.modems or your local dealer: there are simply
too many products to describe here.
[1.2] What kind of cable do I need to use my external modem with my Macintosh?
------------------------------------------------------------------------------
Most modems have a female DB-25 (25 pin) connector labelled
RS-232C on their backsides. All Macintoshes since the Mac Plus
use a mini DIN-8 (8 pin) connector for the two serial ports
(modem and printer). Earlier models use the larger DB-9 (9 pin)
connector. Finding a generic cable for any configuration should
not be very difficult at most computer accessory stores. They
are typically sold for around $25.
However, especially at the higher bps rates (9600 bps and up),
a hardware handshaking cable is highly recommended. Attempting
to transfer files at high bps rates using a non-hardware-
handshaking cable will likely result in repeated transmission
errors, a drop in the transfer rate, and possibly an aborted
transmission. Since many non-hardware-handshaking cables are
still being sold, it's a good idea to ask before buying.
One hardware handshaking cable available by mail-order is the
CompUnite High-Speed Mac modem cable, available for $14 (as of
8/94) from Celestin Company (see the end of Part 4 of this FAQ
for vendor information). This product has been listed as a BMUG
(Berkeley, California Macintosh User's Group) Choice Product.
If you want to "roll-your-own" or are having problems getting
your modem and your Macintosh to communicate, read on. The
serial ports on the Macintosh are not actually RS-232C ports
but are instead RS-422 compliant, a similar but better standard.
This explains some of the difficulty in implementing hardware-
handshaking.
One way to wire your cable is as below:
Macintosh (DTE) Modem (DCE)
DIN-8 DB-25
Pin Signal Signal Pin
1 HSKo --------------------------- RTS 4
2 HSKi --------------------------- CTS 5
3 TxD- --------------------------- TxD 2
4 GND --------------------------- GND 7
5 RxD- --------------------------- RxD 3
6 TxD+ (nc) .-- DSR 6
7 GPi (nc) '-- DTR 20
8 RxD+ --------------------------- GND 7
shield --------------------------- shield
Figure 1.2.1
If your modem cannot be configured to ignore DTR, or if you
are using an old 1200 bps or 2400 bps modem, the pinout in
Figure 1.2.1 is probably best. However, if you are using a
high-speed modem that can ignore DTR, and/or Remote AppleTalk,
you should instead use the pinout in Figure 1.2.2, which is
the pinout "recommended" by Apple:
Macintosh (DTE) Modem (DCE)
DIN-8 DB-25
Pin Signal Signal Pin
1 HSKo ----------------------+---- RTS 4
'---- DTR 20
2 HSKi --------------------------- CTS 5
3 TxD- --------------------------- TxD 2
4 GND ----+---------------------- GND 7
8 RxD+ ----'
5 RxD- --------------------------- RxD 3
6 TxD+ (nc)
7 GPi --------------------------- DCD 8
shield --------------------------- shield
Figure 1.2.2
Note: You can find a pretty picture of this PICT by using
ResEdit to open the Apple Modem Tool Extension CTB tool.
Note: Be careful! Although technically, you should not be able
to damage either your modem or computer by using an incorrectly
wired cable, you should always perform a connectivity test to
double-check your wiring before using your homemade cable.
Some serial devices place auxiliary voltages on non-standard
pins.
Note: If you are having trouble finding or soldering a mini DIN-8
connector (they can be expensive and are rather small), it is
suggested you purchase a straight-through DIN-8 to DIN-8 cable
(often sold for use with serial port switches), cut it in half,
and wire each end to a DB-25 connector that can plug into your
modem (resulting in *two* cables).
Note: The GPi pin is connected on almost all Macs (exceptions
include the Mac Plus and Mac LC). Most software does not use this
pin, however.
Note: If you are running A/UX and are having difficulties
controlling your modem from software, see the comp.unix.aux FAQ
for the latest information on an A/UX specific cable.
Many people routinely ask for a pinout diagram for the mini DIN-8
connector; Figure 1.2.3 shows the pinout as if you were looking at
the (female) connector on your Macintosh; the (male) cable connector
will be a mirror image. (Figure artwork by Ben Cranston)
Mini DIN-8 Macintosh Serial Connector Pinout
/------###------\ 1 HSKo Output Handshake
/ ### \ (Zilog 8530 DTR pin)
/ \ 2 HSKi/CLK Input Handshake *OR*
/ [|] [|] [|] \ External Clock
/ 8 7 6 \ 3 TxD- Transmit data (-)
| |
| | 4 Ground Signal ground
| === === === |
| 5 4 3 | 5 RxD- Receive data (-)
| |
| | 6 TxD+ Transmit data (+)
\----+ === === +----/
\###| 2 1 |###/ 7 N/C (no connection)
\##| |##/
\| |/ 8 RxD+ Receive data (+)
\------###------/
###
Figure 1.2.3
Finally, it should be noted that there is no *best* RS-422 to
RS-232 cable. You'll see many different wiring diagrams posted
to Usenet. Each usually has its own purpose and champion; the
two given in this FAQ, however, are fairly generic and one or
the other should work with most modems being sold today.
[1.3] What do V.32, V.42, bis, MNP, etc mean?
---------------------------------------------
Because these topics are universal telecommunications issues,
they are more fully discussed in comp.dcom.modems. However, a
short description of some of the more common abbreviations and
buzzwords is given below.
An excellent article on the subject of modems, including
a guide to buying high-speed modems, is available from
InfoMac (sumex-aim) and its mirror sites as the file
info-mac/comm/info/modem-guide-11.hqx.
Buzzword What it typically means
--------------- ----------------------------------------------
bit : binary digit; amount of information necessary
to distinguish between two equally likely
events (such as the value of a binary digit)
byte : eight bits; size of a single ASCII character
bps : bits per second
baud : one analog signal state change; people usually
use baud and bps interchangeable, although most
modern modems can encode multiple bits per baud
Bell 103 : 300 bps U.S. Standard
Bell 212A : 1200 bps U.S. Standard
LAP/M : Link Access Protocol/Modem.
MNP : Microcom Networking Protocol (Proprietary)
MNP5 : MNP extension; 2 to 1 data compression.
V.32 : 9600bps, 4800bps
V.32bis : 14.4Kbps, 12Kbps, 9600bps, 7200bps, 4800bps
V.32terbo : psuedo-standard extending V.32bis to 16.8, 19.2 kbs
V.34 : 28,800 bps, 14,400 bps, 9,600 bps, 2,400 bps
V.Fast : Interim version of V.34; sometimes used as a nickname
for V.34
V.FC : A proprietary Rockwell protocol used before V.34 was
approved as a standard
V.42 : MNP 4 and LAP/M modem to modem error correction
V.42bis : LAP/M and 4-to-1 data compression.
Note: Some V.FC modems do not work with V.34 modems at 28,800 bps.
[FAX standards:]
V.21 : 300 bps FAX
V.27ter : 4800 bps FAX
V.29 : 9600 bps FAX
V.17 : 14400 bps FAX
Table 1.3.1
[1.4] How fast can the Macintosh serial ports really go?
--------------------------------------------------------
The Macintosh operating system supports data rates up to 57600 bps,
but the Macintosh serial hardware can support transfer rates that
are much higher if they are externally clocked. Serial port
sound-input-devices such as the Cedar Technologies SID and
Farallon's MacRecorder, as well as AppleTalk boxes, use this trick
to achieve transfer rates greater than 100 Kbps.
Ward McFarland <70240.504@compuserve.com> writes:
"The clock rate supplied by pre-AV Macs to the SCC (and used for bps
rate generation) limits the maximum asynchronous serial speed to
57,600 bps. The maximum synchronous speed is 16 times this (as used
by the old serial hard drives used on 512K Macs and by the Personal
LaserWriters).
Indeed, the SCC can be externally clocked to faster asynchronous
speeds, with a couple of limitiations. First, the external clock
is applied to the Mac's CTS input, making it impossible to respond
normally to normal modem handshake requests. Second, since the SCC
used in older Macs can only buffer 3 characters, data losses can occur
due to interrupt service delays. MacRecorder and other custom devices
got around this by locking out all system interrupts during serial
data transfer.
The AVs and PowerMacs apparently use a different SCC clock, and I have
benchmarked fairly good ZModem performance using Smartcom II 4.0 at
115,200 and 230,400 bps. Apple does not publish the serial driver
control call to set this, and they state they do not support such
speeds. I do not know of anyone besides Hayes who has managed to get
Apple to tell them the methodology.
Creative Solutions, Inc. [see the end of Part 4 of this FAQ for vendor
contact information] makes a NuBus card (the "Hustler") and soon will
make an external SCSI-based device that can support 2 channels at
115,200 bps or one at 230,400 bps. This is currently used by quite
a number of people supporting high speed (28.8) modems and direct
serial connections. This product works fine with existing
communications and bulletin board system software."
Note: Powerbooks are known to have problems at extremely high
data rates. These problems are caused by Power Manager overhead.
System 7.1 is supposed to solve or alleviate these problems.
Note: AppleTalk being active can degrade serial port performance,
as can Ethernet-network traffic. Turning off AppleTalk via
the Chooser, or disconnecting the Ethernet transceiver, are
work-arounds.
[1.5] How can I disable call-waiting when using my modem?
---------------------------------------------------------
This varies depending on your local phone company, but often,
if you preced the phone number you wish to tone dial
with "*70," (omit the quotes but not the comma), you can
disable call-waiting FOR THAT CALL ONLY.
If you have a strictly rotary dial line, try preceding the
phone number with "1170".
In the United Kingdom, the code to use is #43#.
If you are using Telecom Australia,
ATDT#43#,;H Will turn call-waiting OFF
ATDT*43#,;H Will turn it back ON again.
================================================================================
[2] File Formats and Conversion
===============================
[2.1] What is a resource (or data) fork?
----------------------------------------
A Macintosh file has two parts: a data fork and a resource fork.
Text files and GIF image files are examples of Macintosh files
that are usually stored completely in the data fork, and have
an empty (or nonexistent) resource fork. Applications, as a
a counter-example, store most if not all of their information
in 'resources' in the resource fork and usually have an empty
data fork.
Because this two-forked organization of files isn't very common,
transferring Macintosh files that have non-empty resource forks
to non-Macintosh machines (such as UNIX boxes, or MS-DOS machines)
requires special encoding, described below.
[2.2] What is MacBinary?
------------------------
MacBinary is a standard way of taking a Macintosh file (both
resource and data forks) and creating a new file with just
a data fork. This new file can then be transferred through
machines which know nothing about the native Macintosh file
system, without losing the information stored in the resource
fork.
MacBinary also stores other information (such as the filename,
creation and modification dates, file type and creator) about
the original file.
If you want to store some Macintosh files on a non-Macintosh
computer, one way is to convert them to a MacBinary format file
before transferring. Note that MacBinary files are useless to
people who are not using Macintosh computers. MacBinary's
purpose is to encapsulate *all* information contained in a
Macintosh file for transport over a non-Macintosh medium. For
this reason, you should not use MacBinary and/or BinHex to
post GIF images, for example, to Usenet because (1) GIF images
contain no Macintosh specific information and (2) doing so will
make it impossible for most non-Macintosh users to display your
image.
Although a Macintosh program (called MacBinary) does exist
to do the converting to and from MacBinary, almost all modern
Macintosh telecommunications programs have the capability of
converting and unconverting MacBinary files for you. ZTerm,
for example, can be configured to automatically detect when
a MacBinary file is being received and to convert this file
to its original representation; or, if you are uploading,
ZTerm can optionally encode the file into MacBinary before
sending. Fetch, White Knight, and most other commercial and
shareware products have equivalent or similar capabilities.
Dennis Brothers designed the original MacBinary standard many
years ago. Yves Lempereur incorporated this standard into
his Binhex 4.0 program (see [2.3]), solving a major problem
on Compuserve. About a year later, around the time the Mac Plus
came out, group discussions on Compuserve led to an enhancement
of the original MacBinary standard. Since then, BinHex 4.0 and
the new MacBinary have become the standard way of encapsulating
Macintosh files for transferring over foreign systems throughout
the Internet, Usenet, and elsewhere.
MacBinary I is the name given to the old MacBinary standard.
MacBinary II is the name given to the new MacBinary standard
which everybody uses today; in common usage, MacBinary means
MacBinary II.
[2.3] (a) What is BinHex? (b) What is uuencode? (c) What are atob/btoa ?
------------------------------------------------------------------------
(a) A "binary" file is usually intended to describe a file which
does not always have the high bit in each byte set to zero.
Text and BinHex files are the most common examples of non-binary
data. Programs and images are common examples of binary data.
MacBinary files are specially encoded binary files (see 2.2]).
Unfortunately, many network e-mail and Usenet gateways are only
receptive to non-binary files. To make it possible to send
binary files such as Macintosh MacBinary files through e-mail
or Usenet, it is necessary to convert these files to a text-
compatible form. BinHex and uuencode are two different ways
of doing this. Both BinHex and uuencode result in files that
are larger than the original binary version.
BinHex 4.0, by Yves Lempereur, is a binary to text translator
that can directly encode any Macintosh document (ie: it knows
how to convert information in both the resource and data forks).
BinHex files can be easily recognized since they begin with the
line:
(This file must be converted with BinHex 4.0)
and are followed by a line starting with a colon, ':'. The
BinHex encoding of the file follows, and is ended with another
colon.
There is in fact a program called "BinHex 4.0" in various
archives, but you don't have to use it to convert files to and
from BinHex. In fact, due to some bugs, it's best to use some
of the other more powerful utilities, such as HQXer, DeHqx,
StuffIt Expander and other StuffIt programs, and Compact Pro,
to name only a few. UNIX utilities (see [6.5]) that manipulate
BinHex, MacBinary, and other types of Macintosh files are also
available. StuffIt Expander has the advantage of also being able
to automatically expand StuffIt, Compact Pro, and Applelink
archives.
Just about every Macintosh program posted appears as a BinHex
archive. Some Macintosh archives also store their files in BinHex
to allow users who don't have (or forget to use) binary mode in
FTP to succesfully transfer files.
BinHex files are denoted by the suffix ".hqx". The specifications
to BinHex, should you be an interested programmer, are available
at the University of Michigan's Macintosh archive site as
mac/misc/documentation/binhex4.0specs.txt, or at InfoMac sites
as dev/info/binhex-40-specs.txt .
There is also a program/format called "BinHex 5.0"; it is NOT
a more advanced version of "BinHex 4.0" but rather a separate
_binary_ format (it uses the entire eight-bit ASCII character
set and is thus not suitable for news postings or e-mail)
that was the precursor to MacBinary (see [2.2]). Converting
a file with BinHex 5.0 and then using BinHex 4.0 is another way
of converting a native Macintosh files with data and resource
forks into a format that can be e-mailed or posted (and then
reconstructed). MacBinary, however, is almost always used in
preference to BinHex 5.0.
(b) "uuencode" is a binary to text translator that serves the
same purpose as BinHex, except that it knows nothing about the
Macintosh resource/data fork structure. uuencode was designed to
allow UNIX binary files to be easily transferred through text-
only interfaces, such as e-mail. Every uuencoded file contains
a line similar to:
begin 644 usa-map.gif
followed by a series of lines of ASCII text characters (which
are normally 60 characters long and begin with the letter 'M').
The file ends with a line containing the word 'end'. There may
be other special keywords included. Usually, one won't find
Macintosh files in uuencode format; however, most non-Macintosh
specific binary data posted to Usenet is uuencoded, so if you
wish to use any of this data (such as the images posted in
alt.binaries.* and elsewhere), you will need to deal with
uuencode. The programs 'uuencode' and 'uudecode' exist on most
UNIX systems. If not, ask a local expert to find them. Several
programs allow you to convert to and from uuencode using your
Macintosh; among these are UUTool 2.3.2 and UULite 1.7.
uencoded files are usually denoted by the suffix ".uu".
There is a StuffIt translator to handle uuencode conversion.
StuffIt Expander 3.5.2 with DropStuff and Expander
Enhancer 3.5.2 will also decode a uuencoded file.
uuUndo, distributed with John Norstad's NewsWatch 2.0b13,
will also decode a uuencoded file.
(c) atob and btoa are programs typically found on UNIX systems
that also convert between binary and ASCII-printable character
sets. Although not as popular as uuencode, btoa produces smaller
text-compatible versions of binary files that can be e-mailed or
posted on Usenet. Check your local man pages for details.
There are StuffIt translators to handle atob/btoa conversion.
[2.4] What is Apple-Single/Double ?
-----------------------------------
AppleDouble is another means of storing Macintosh files on
non-Macintosh computers or filesystems, particularly on UNIX
filesystems that also allow files to be mounted under the
Macintosh operating system via AppleShare (or an equivalent
product).
AppleDouble files are actually two files. The data fork
of the corresponding Macintosh file is stored in a single
file just as it exists on the Macintosh using the original
filename. The resource fork is stored in a second file whose
name is obtained by prefixing the original filename with '%'.
More extensive documentation is available at
ftp.support.apple.com.
A few Macintosh programs decode these files; one such utility
is Tiger 1.11. The macutils UNIX utilities [see 6.5] may also
be useful. Eudora 1.4 and later also handles this format.
If you are trying to figure out how to access the files in
the 'mac.bin' directory at ftp-archive maintained by the
University of Michigan, don't bother; all those files exist
in .hqx format in the 'mac' directory.
[2.5] What do file suffixes like .hqx, .sit, .bin, etc ... mean and how
-----------------------------------------------------------------------
can I convert such files back to normal Macintosh applications
and documents?
Most files available by FTP or posted to Usenet are modified
twice to allow them to more easily pass through foreign computer
systems. Files may be compressed to make them smaller, and/or
they are almost always translated to either BinHex (.hqx) or
MacBinary (.bin) format (see [2.2] and [2.3] for an explanation
of these formats).
How a Macintosh file has been translated and compressed for
transmission is indicated by its suffix. Normally a file will
have a name similar in form to: filename.xxx.yyy, where:
.xxx indicates how it was compressed
.yyy indicates how it was translated
Usually, .xxx is one of: .cpt, .dd, .sea, .sit
Usually, .yyy is one of: .bin, .hqx, .image
To convert a file back to its native Macintosh format, you will
typically need to go through one step per suffix. For example,
the filename "Swatch.cpt.hqx" indicates that a Compact Pro
archive (.cpt) "Swatch" has been translated to BinHex (.hqx).
To recreate the file(s) in the original archive, you must
first 'undo' the BinHex transformation, creating a Compact Pro
archive, and then open the Compact Pro archive and extract
the file(s) in the archive.
You can use the following table to determine what Macintosh
programs decode which formats. For a more complete description
of the various Macintosh archival programs, see the excellent
FAQ for comp.sys.mac.apps.
(This table was contributed by Bruce Grubb <bgrubb@scf.nmsu.edu>.
Regular updates of this list can be found at sumex or any of its
mirror sites, in the /info-mac/comm/info directory. The filename
is of the form mac-ftp-list[version #].hqx. You can find the format
chart by itself, in the same places, as format-chart-[version #].txt.)
Programs for the Macintosh
--------------------------
unix gzip .uu/
Macintosh .cpt .sit .hqx .bin .zip .arc .tar .Z .gz/.z .uue
Stuffit Expander* D D D D
w/ DSEE* D X X X D D D D D
StuffIt Lite** D X X X {see note below}
StuffIt Deluxe** D X X X D D X X D X
SITcomm D X X X D D X X X
ArcMac X
BinHex 4.0 X
BinHex 5.0 D X
Compact Pro 1.5.1 X D/N X
Extractor 1.2.1 D D/N D
HQXer 1.1 X
MacCompress X
MacGzip D X
ShrinkWrap 1.3.2*^ D D D D D D D D D
SunTar 2.0.4 X X X D
Tar 4.0b X
UnZip D
UU Lite X
uucd 2.3 X
UUTool X
uuUndo D
ZipIt 1.3.2b1 D D X
Programs for other computers
----------------------------
Other unix gzip .uu/
computers .cpt .sit .hqx .bin .zip .arc .tar .Z .gz/.z .uue
extrac.exe D
macutil (unix)
hexbin D D
macunpack D D/U D D
mcvert (unix) X X
PKZIP X
unsitins.exe D
N = Cannot decode .sit dlx {Type SITD} files
D = Decode only
X = Encode and decode
U = Uncertain or Unknown
.sit refers to both 1.5 and dlx. Otherwise a '/' is used {1.5/dlx}.
Note: Almost every Mac communications program can decode .bin files.
* DropStuff with Expander Enhancer is an $30 shareware addon for
Stuffit Expander. DSEE is also used by other programs {marked with a *^}
to expand files. Current versions are 3.5.2 as of this writing.
** Stuffit Deluxe translators can be used with Stuffit Lite. Current
versions are 3.5.0 as of this writing.
Table 2.5.1
Special note: .hqx, .txt, and .uu files are the ONLY files that can be
downloaded in ASCII mode; all others must be downloaded in BINARY mode for
the file to decompress properly. Otherwise you will get errors such as
"unreadable file" or "file is corrupt" when you try to decompress them.
Note also: StuffIt Deluxe now includes translators for .tar, .uu,
MacBinary, atob, btoa, AppleLink packages, AppleSingle, DiskDoubler,
and UNIX compress. These translators can also be used with StuffIt
Lite. .arc and .zip translators are also distributed with StuffIt
Deluxe, but remain part of the commercial package.
StuffIt Deluxe and StuffIt Lite 3.5.0 no longer support DiskDoubler
files. (1/95)
The following file suffixes indicate formats that are native
to the Macintosh and which can be manipulated using the indicated
programs:
.bin MacBinary files; see [2.2]
.cpt Compact Pro archive files; [see 3.6]
.dd DiskDoubler archive files; [see 3.6]; DDExpand, DiskDoubler
.hqx BinHex files; see [2.3], [3.7]
.image Apple DiskCopy disk image file (typically used for
distributing system software); latest version available
via anonymous ftp from ftp.support.apple.com; can also be
"mounted" as regular volumes with MountImage and ShrinkWrap
.pit Packit files; [see 3.6]; an old compression format
which has been replaced by .sit. In general, a program
that handles .sit files can decode .pit files as well.
.pkg AppleLink package files, replaced by .sit. StuffIt to decode.
.sea Self-extracting archive files; this usually denotes an
application which can be double-clicked upon to create
a decompressed version of the archive, without the need
for any decoding program
.sit StuffIt archive files; [see 3.6]
.sitd mistakenly used to indicate files created by StuffIt
Deluxe; *all* StuffIt files should be given the .sit
extension (says the author!)
Table 2.5.2
The following file suffixes indicate formats that are not native
to the Macintosh, but in most cases, files of these types can
be manipulated on the Macintosh using the indicated programs.
.arc MS-DOS PC archive file; ArcPop, MacArc, SE+DS+EE
.arj MS-DOS PC archive file (more common in Europe than U.S.);
unArjMac, DeArjl
.gif Compuserve Graphics Interchange File; many programs,
free, shareware and commercial exist to display and/or
modify these images; some of the popular shareware ones
are: QuickGIF and GIFConverter.
.lha Amiga or old MS-DOS PC archive file; MacLHa
.lzh Amiga or old MS-DOS PC archive file; LHarc, MacLHa, Macunpack
.shar UNIX shell archive file; Unshar 1.5
.uu UNIX uuencoded files; see [2.3]
.Z UNIX 'compress' archive file; MacCompress 3.2, SE+DS+EE
.gz GNU ZIP file; typically created on UNIX; MacGzip, SE+DS+EE
.z Early suffix for GNU ZIP files. Due to confusion with the UNIX
'compress' suffix {.Z} it was abandoned in favor of the .gz suffix.
.zip MS-DOS PC archive file; UnZip, ZipPop, ZipIt, SE+DS+EE
.taz A common abbreviation for .tar.Z
.tgz A common abbreviation for .tar.gz
.txt ASCII text file
.zoo - old {~1989} PC/Amiga format, replaced by .arc; MacZoo, MacBooz
to decompress
! "SE+DS+EE" means StuffIt Expander 3.5.2 with DropStuff and Expander
Enhancer 3.5.2 (StuffIt Expander is free, and DropStuff with
Expander Enhancer is a $30 shareware product).
Note: .gz and .Z compression systems, while both native to UNIX, are
completely different, and these suffixed may not be interchanged.
Table 2.5.3
[2.6] How can I use a binary-downloaded file that appears as an
unusable text file on the Mac desktop?
-----------------------------------------------------------------------------
Celeste Dolan <celeste.dolan@ledge.com> responds:
A familiar problem, and one I've seldom been able to solve by changing
the file type and creator of the "text file." The -39 is a "logical end
of file" error, for what that may be worth.
I know of two methods that will restore the PC-downloaded file to a file
that your Mac will recognize. Method #1 requires Apple File Exchange,
which comes with your System Software set on the "Tidbits" disk. It also
requires the Mac-to-MacBinary/MacBinary-to-Mac set of translators for
AFE, which do NOT come with AFE on the System set. I found them on AOL a
couple of years ago, but they are probably available at some of the
usual ftp sites. Put the translators in the same folder as AFE and open
AFE. Make sure BOTH drive windows are active and choose "MacBinary to
Mac" from the menu called either "Mac to Mac" (if you don't have a DOS
disk in your floppy drive or you're running something like PC File
Exchange that lets you access DOS disks from the desktop) or "PC to Mac"
(DOS disk in floppy drive and no DOS-mounting software running).
Highlight the file that needs fixing and hit the "translate" button in
the center of the screen. The translated file will have its proper Mac
icon and behave the way you expect it to.
Method #2 uses StuffIt. I have tested this with StuffIt Deluxe 3.0.7,
but not with StuffIt Lite 3.0.7 (shareware version). Open StuffIt, and
make sure you have your preferences set to show the "Translate" menu. Go
to this menu and choose "MacBinary" from the translator list. A submenu
with the choices "encode" and "decode" will appear. Hold down the OPTION
KEY, choose "decode" and navigate to the file you want to fix. (In my
experience, the file may not show up in the window if you don't hold the
OPTION key down.) Tell StuffIt to open the file and then where to save
the decoded file. Save, and you'll have a usable file.
Patrick Hoepfner <hoepfner@haiti.gsfc.nasa.gov> adds:
Method #2 1/2. Drop the file onto StuffIt Expander.
================================================================================
[3] Macintosh File-transfers
============================
[3.1] What programs support Kermit, FTP (client), and/or X,Y,Z-MODEM
--------------------------------------------------------------------
and where can I get them?
The following is a fairly complete list of the popular free, shareware,
and payware terminal and file-transfer programs currently available.
(Last revised: 6/94, but this list is probably not complete).
CL: Communicate Lite, $50 SRP, various discounts available,
Mark/Space Softworks, mspace@netcom.com
CM: Comet, free, Cornell University
comet-comments@nmc.cit.cornell.edu;
FTP from ftp.cit.cornell.edu
GT: GrafTerm, $50 shareware, Infrastructure Software
MI: MacIntercomm, $130, New World Computing, Inc., (818) 999-0607,
help@inter.com
MK: MacKermit, free, source code is available, fdc@watsun.cc.columbia.edu
ML: MacLayers 1.30, free, UNIX source included, Eric C. Rosen and
David W. Trissel, layers-reply@rascal.ics.utexas.edu
MT: MacToPic Plus, $295, site licenses available, Carnation Software,
(206) 333-4288, richlove@netcom.com
MP: MicroPhone II 5.0, $149 retail, $119.95 mail order; cheaper sidegrades
often available, Software Ventures Corporation, (510) 6441325,
microphone@svcdudes.com
Also, MicroPhone Pro, a slightly more capable package.
Software Ventures Corporation now offers MicroPhone LT, a streamlined
version of MicroPhone II.
PT: PacerTerm, $159, Pacer Software, (619) 454-0565,
support@pacersoft.com
PW: Pathway Access Macintosh, The Wollongong Group, (800) 872-8649
[in California (800) 962-8649], sales@twg.com
QV: QVT, $50 shareware, QPC Software
SC: Smartcom II, $84, $59 upgrade from Smartcom, Hayes,
(404) 441-1617, BBS: 800-US-HAYES
ST: SITcomm 1.0, $120, sidegrades are $49, and existing Aladdin customers
pay only $39, Aladdin Systems, (408) 761-6200,
aladdin@applelink.apple.com or aladdin@well.sf.ca.us
TM: Term, free, Peter DeCamillo and Jon Gilbert
cmsmaint@brownvm.brown.edu
TL: Terminal, free, source code included, Erny Tontlinger
73720.2200@compuserve.com
TR: Termulator, $25 shareware, Brad Quick
TY: Termy, free, Ice Engineering, termy@ice.com
VP: VersaTerm Pro, $177, Synergy Software, (215) 779-0522,
tech support: synergy1@tech.abelbeck.com,
upgrade order forms: upgrade@synergy.com, sales information:
maxwell@sales.synergy.com
VT: VersaTerm, $90, Synergy Software, (215) 779-0522
tech support: synergy1@tech.abelbeck.com,
upgrade order forms: upgrade@synergy.com, sales information:
maxwell@sales.synergy.com
WK: White Knight, 68k - $85; Power PC - $109.95, Freesoft, (412) 846-2700
ZT: ZTerm, $30 shareware, $40 with disk, Dave Alverson,
davea@xetron.com
5P: 5PM, $370, About Software Corporation, diane@ascus.com
(408) 725-4249
The archive sites described in the Appendix are the best place
to look for free or shareware file-transfer programs. Other
commercial but non-shareware ("payware") products must be
purchased from a dealer or the company directly.
Table 3.1.1 summarizes file transfer capabilities of various
Macintosh telecommunications programs.
Programs: ZT SC MP ST VT VP WK TR PT GT ML MK QV TM TL TY CM 5P MI CL MT PW
-----------------------------------------------------------------------------
Protocols |
__________|
XMODEM | X X X X X X X X X X X X X X X X X
YMODEM | X X X X X X X X X X X
ZMODEM | X X X X X X X X X X X X X X
Kermit | X X X X X X X X X X X X X
QuickB | X X X ! X X
B Plus | X X X X
FTP | X X X X X X
TFTP | . . . . . . . . . . . . . . . . X . . . . X
rmac/wmac | . . . . . . . . . . . . . X . . . . . . . .
Flash | . . . . . . X . . . . . . . . . . . . . . .
FT3270 | . . . . . . . . . . . . . . . . X . . . . .
CTB tools | X X X X X X X
! White Knight supports the QuickB protocol through an
FTP-able external RCMD module, NewQuickB.PROC.
Table 3.1.1
Table 3.1.2 summarizes the terminal-emulation capabilities of
various Macintosh telecommunications programs:
Programs: ZT SC MP ST VT VP WK TR PT GT ML MK QV TM TL TY CM 5P MI CL MT PW
-----------------------------------------------------------------------------
Terminals |
__________|
TTY | X X X X X X X X X X X X X X X
VT52 | X X X X X X X
VT100 | X X X X X X X X X X X X X X X X X X
VT102 | X X X X X X X X X X X X
VT220 | X X X X X X X X X
VT320 | X X X X *
VT420 | . . . . . . . . . . . . . . . . . X . . . .
PC/ANSI | X X X . . . X . . . . . . . . . . . X . . .
IBM3270 | X X X X X
IBM5250 | . . . . . . . . . . . . . . . . . X . . . .
Tek 4010 | X X X
Tek 4014 | X X X
Tek 4105/7| . . . . . X . . . . . . . . . . . . . . . *
TVI950 | X X
DG210/211 | X X
Prestel | . X . . . . . . . . . . . . . . . . . . . .
Controls | X X X . . . . . . . . . . . . . . . . . . .
CTB tools | X X X X X X
Viewpoint | . . . . . . . . . . . . . . . . . . . . X .
Wyse 50 | X X
Prism | . . . . . . . . . . . . . . . . . . . . X .
Table 3.1.2
* optional
Table 3.1.3 summarizes the scripting capabilities of various
Macintosh telecommunications programs:
Programs: ZT SC MP ST VT VP WK TR PT GT ML MK QV TM TL TY CM 5P MI CL MT PW
------------------------------------------------------------------------------
Scripting |
___________|
Recording | X X X X X X X X
If/Else | X a X X X X X X X
Loops | X a X X X X X X
XCMDs | X X X X X
FileOps | X a X X X X X X
Arithmetic | X a X X X X X X
Variables | X X a X X X X X X X
User Input | X a X X X X X X X
Key Remaps | X X X X X X * X
Arrays | X a ! X X
Wait/Send | X a X X X X X
AppleScript| X X
a denotes capability is accessible through AppleScript
Table 3.1.3
Note: SITcomm is fully AppleScript-able (all features can be
controlled through AppleScript). The Frontier Runtime portion
of the Frontier scripting system is also bundled with SITcomm.
! Although PacerTerm does not support arrays per se, it
does implement HyperTalk's chunk expressions that allow
any variable to be referred to as a collection of
characters, items, words, or lines.
* Allows programmable function keys
The February, 1993 issue of "MacUser" reviews White Knight,
MicroPhone II, Smartcom II (for the Macintosh), ZTerm, and
MacIntercomm. The review is also useful for those new to
telecommunications in general.
Peter Newton's DialScript 1.7, archived at rascal.ics.utexas.edu,
is a telecommunications scripting utility useful for automating
complicated logins and then automatically launching applications
or startup documents. It's free and the source is available.
Table 3.1.3 summarizes some additional features of various
Macintosh telecommunications programs.
Programs: ZT SC MP ST VT VP WK TR PT GT ML MK QV TM TL TY CM 5P MI CL MT PW
-----------------------------------------------------------------------------
Feature |
__________|
PowerMac | X X
Drag&Drop | X X
PowerMac = Power Mac Native
Drag&Drop = Supports Drag & Drop
Table 3.1.3
[3.2] What is the latest version of ZTerm? How can I find out more about ZTerm?
-------------------------------------------------------------------------------
ZTerm is currently at revision level 1.0b3 (9/94), a public beta.
Other recent versions are 0.94 and 0.95.
Two "fake" versions of ZTerm have circulated. Recently (4/93),
a hacked version called "ZTerm 0.93 XK", based on 0.9, was
distributed.
An older also fake version labelled "ZTerm 1.0" has also been
seen. Neither versions were released by the author, Dave Alverson.
For the latest scoop on ZTerm, as well as advice on features, bugs,
bug fixes, and more, see Leslie Jones' ZTerm FAQ which is posted
to comp.sys.mac.comm, comp.sys.mac.apps, news.answers, and the
InfoMac and UMich archives. At present its home FTP site is at
ftp://usit.net/pub/lesjones/ZTermFAQ-##.txt where ## is the version
number.
[3.3] What is the Communications Toolbox (CTB)?
-----------------------------------------------
The Communications Toolbox is a Macintosh operating system
interface that provides a standard interface for programmers
writing communications programs. Rather than make calls to
control the modem serial port, for example, a programmer can
call an equivalent CTB routine. This allows the operating system
to manage the serial port(s) just like any other limited
resource. In addition, specific "tools" that interface with
modems, provide terminal emulation, or handle file transferring
can be implemented as external add-on features to CTB-aware
programs.
The CTB requires System 6.0.4 or later. The CTB is built into
System 7. Tools can be added by placing them in the Extensions
folder; rebooting is not necessary. Under System 6.0.X, CTB
tools belong in the Communications folder.
[3.4] Are there any shareware or freeware tools that support Kermit,
--------------------------------------------------------------------
and/or X,Y,Z-MODEM?
Termy 3.2, freeware from Ice Engineering, is one of two CTB-aware
application that can be obtained via anonymous FTP. Termy has
no built-in support for any connection methods, file transfer
protocols, or terminal emulation, so you will need to obtain
Communication Toolbox tools for each of these.
WendyComm 2.0 is another CTB-aware application available via
anonymous FTP.
Tim Endres has written and released TGE TCP Tool, a Connection
Tool for the Communications Toolbox. It provides TELNET and
transparent TCP connections. The tool is free for personal use.
Several modem Connection tools are available from the various
FTP sites. These include the Apple Modem Tool 1.5.4, the Hayes
Modem Tool 1.02, the CCL Modem Tool 1.0, and the Zoom Modem
Tool 1.11. After recently releasing his CTB File Transfer tool,
Kermit Tool GH (which supports MacBinary, RLE compression,
and other features), Glenn Howes has gone on to release a YMODEM
tool.
The Basic Connection Tools Disk is available from
ftp://ftp.support.apple.com/pub/apple_sw_updates/US/mac/
n_c/comm_toolbox_tools/comm_toolbox_tools/BCS (1.1.1).hqx.
You will need DiskCopy or MountImage to decode the image file.
This disk includes VT102 and TTY terminal tools, XMODEM and Text
File Transfer tools, and Modem, Serial, and Appletalk
Connection tools (10/92).
Advanced Software Concepts has demonstration versions of
several CTB tools at InfoMac sites in the demo directory.
Demo versions of a TCP/IP Connection tool, an FTP File Transfer
tool, as well as VT420, IBM3270, and IBM5250 Terminal tools
are being distributed (10/92).
Stalker Software has a demonstration version of its VideoTex
terminal tool at InfoMac sites. Stalker has also released a
free CEPT Modem Tool, which is equivalent to the CCL Modem Tool
but also supports the CEPT-1 low-level protocol used by European
VideoTex systems.
New free and shareware CTB tools inevitably get posted to Info-
Mac where they appear in the info-mac/comm directory and also
to mac.archive.umich.edu in mac/system.extensions/commtoolbox.
If you give the command "ls *tool*" in these directories
through an anonymous FTP connection, you can get a list of
all the free and shareware CTB tools currently available.
Mark/Space Softworks offers an archive of Apple Modem Tool modem
definitions for Supra, Global Village, Promethus, and a few other
modem brands, along with a DocMaker guide on how to use them. This
"Modem Definitions Collection" file can be found at info-mac archives
as well as at the Mark/Space Softworks anonymous ftp site:
ftp.netcom.com:pub/ms/mspace.
There are also a number of available *payware* tools:
o Mark/Space Softworks has developed a ZMODEM CTB tool (along
with XMODEM and YMODEM tools). A demonstration version of the
ZMODEM tool is available for anonymous FTP with the restriction
that uploading is not supported. The demo is available in the
Communications directory at Info-Mac FTP sites, among other places.
o MacToPic Plus supports the CommToolBox and can transfer to
machines using Ethernet, AppleTalk, and TCP/IP networks, as well
as regular dialup lines. It includes
XMODEM, YMODEM, ZMODEM, Kermit, and FTP file transfer protocols.
It can emulate Viewpoint, Wyse 50, VT101, and Prism terminals.
The emulators support video attributes such as dim, reverse, underline,
132-column codes, and graphic characters sent from the host computer,
as well as enhanced Viewpoint mode. It supports 25 special commands
that can be sent from the host to the Mac to initiate data transfers,
and display pictures and QuickTime movies under host control.
o MicroPhone Pro includes a Telnet tool (along with some FAX
support software). MicroPhone II does not include the Telnet
tool, unfortunately.
o PacerTerm ships with a broad collection of tools, including:
XMODEM, ZMODEM, Kermit, and FTP file transfer tools; Telnet,
LAT, ADSP, and serial connection tools; and TTY, VT102, and
VT320 terminal tools.
o Seaquest Software has released XMODEM, YMODEM, ZMODEM, and
Kermit file transfer tools.
o SITcomm ships with a full set of CTB tools; included are XMODEM,
YMODEM, ZMODEM, and Kermit file transfer tools, as well as TTY and
VT102 connection tools, and the Apple Modem Tool.
o Versaterm and Versaterm Pro include FTP client and server file
transfer tools and Telnet, LAT, SLIP, and ADSP connection
tools.
o 5PM ships with a Telnet Tool and the Apple Basic Connectivity
Set (XMODEM, ADSP, serial, modem, TTY, VT102, VT320). Other tools
are available from Advanced Software Concepts : FTP, VT420,
IBM3270 and IBM5250.
[3.5] How can I transfer Macintosh files to/from my Macintosh and other
-----------------------------------------------------------------------
non-Macintosh computers (eg: mainframes, UNIX boxes, PCs)?
If your telecommunication program supports MacBinary (they
almost all do), turn MacBinary on. This usually involves
selecting a menu option or clicking a radio button in a
'preferences' type dialog box. Then, transfer your file
normally. Your Macintosh file will be sent as a MacBinary file
that can be treated as an ordinary binary file.
If your telecommunication program does not support MacBinary,
get a copy of the MacBinary program and use it to make a
MacBinary version of your Macintosh file. Then send this
MacBinary file. Meanwhile, look around at the various shareware
and commercial telecommunications programs that do support
Macbinary. See [3.1].
Note: Not all files need to be transferred as MacBinary files.
In particular, most text and non-Macintosh specific binary files
(like GIF/JPEG images) do not. See [2.2] for more information.
To actually "download" a file (eg: transfer it from a remote
host computer to your Macintosh), you must first instruct the
remote computer to send the file by issuing a command. For
example, to download a file from a Unix machine using XMODEM,
you would first have to give a command similar to:
% sx filename
where 'sx' is the local Unix program to send a file using XMODEM
and 'filename' is the name of the file you wish to send. Then,
locally, you must start the file transfer by typically choosing
a menu option in your terminal program. The process is similar
for Kermit transfers. Terminal programs that support ZMODEM
should recognize the start of a ZMODEM download automatically.
Note: Not all systems are alike. The command to start XMODEM
may not necessarily be 'sx'; another possibility is 'xmodem'.
Ask your local system administrator if you cannot find the
right program; most sites support something. Also, see the
listing below.
To upload, first issue the appropriate receive command on the
remote host computer; then, select the local send option in your
terminal program. Good ZMODEM packages can start the remote file
transfer automatically.
If you experience multiple CRC errors when downloading with
ZMODEM, especially after backgrounding the download, try sending
your file using a fixed window size, eg: 'sz -w 1024 filename'.
If errors persist, also try escaping control characters,
eg: 'sz -ew 1024 filename'. Depending on your setup, you may
be able to use a larger window size (eg: use 4096 or 2048
instead of 1024) which can slightly reduce transfer time.
Typical Unix programs that support transfering files via a
serial (modem) link:
Kermit XMODEM YMODEM ZMODEM
------- ------ ------ ------
kermit sx sb sz
ckermit xmodem
If you are trying to transfer a lot of information between
a Macintosh and an MS-DOS PC, and your Macintosh has an FDHD
disk drive (also known as a SuperDrive), using Apple File
Exchange, or any of the various shareware and payware programs
that allow you to access (or even mount) MS-DOS formatted 3.5"
HD diskettes, can greatly speed up the transfering process.
Apple File Exchange even provides for automatic translation
of certain types of files. If you are transfering a lot of
information between a Macintosh and a Unix system, you can
use the (free) Macintosh program suntar to read 1.44 MB Unix
tar floppies.
Note: On most Sun Microsystems' floppy drives, the appropriate
formatting command is "fdformat -ev /dev/rfd0c". This will
verify and eject the disk after formatting. Then use tar to
copy files to the device /dev/rfd0c.
[3.6] What's the best compression program to use when uploading files
---------------------------------------------------------------------
to an archive or BBS? Are there any other guidelines I should
follow?
Best Compression: (Revised 10/94)
---- -----------
The shareware program StuffIt Lite ($25) (and its commercial
sibling, StuffIt Deluxe) are generally regarded as providing
the best compression performance of the many Macintosh
compression utilities. Both programs also sport a fancy
user-interface. Registered users of StuffIt Lite can upgrade
to StuffIt Deluxe for $45, which includes many other compression
tools that are not directly applicable to telecommunications.
StuffIt Expander (free) with DropStuff and Expander Enhancer
($30 shareware) seems to be the most comprehensive package
currently available for decompressing files. StuffIt Expander
and Expander Enhancer are currently at version 3.5.1 as of
10/94.
The shareware program Compact Pro provides similar compression
performance to StuffIt Lite and also has a loyal set of users.
According to Patrick Hoepfner <hoepfner@haiti.gsfc.nasa.gov>,
"CompactPro does a better job of saving an archive across multiple
disks, especially if there are files on the disks that you want
to save."
Individual preferences differ, so the editor suggests you try
using both programs (StuffIt Lite, StuffIt Expander with DropStuff,
Expander Enhancer, and Compact Pro are available
for FTP at the various archives sites) and choose the one you
like best. Note that StuffIt 1.5.1 and Stuffit Classic are
*not* the same as, nor as good as, StuffIt Lite 3.0.
Posting Macintosh Programs: (Revised 4/93)
------- --------- --------
You should use either StuffIt Lite, StuffIt Deluxe, or Compact
Pro to compress Macintosh files you send to anonymous FTP sites
and BBS's. Do not post PackIt, Disk Doubler, SuperDisk, Zip,
or any other type of archive (including self-extracting
archives -- see below). Stuffit Lite 3.0 and Compact Pro
have evolved as the standard archive formats for posting
Macintosh files for good reasons.
Regardless of which archiver you use, PLEASE DO NOT MAKE AN
AN ARCHIVE YOU ARE POSTING SELF-EXTRACTING! The extra code
added to the file to make it self-extracting is NOT insignificant
in size. The convenience of self-extracting archives is not worth
the space they waste at anonymous-FTP sites and BBS's (where
literally thousands of compressed files are stored). Self-
extracting archives are useful in other contexts, but should be
discouraged as a medium for posting to archives. Also, don't
rely on the archive maintainer having the time to extract your
self-extracting post and re-archiving it; these volunteers are
simply too busy to take on this additional burden.
Before you create your archive, set the Finder label of all
files you plan to include in the archive to 'None'.
Avoid using strange punctuation marks in filenames that you
will distribute. Characters such as exclamation points, spaces,
dollar signs, etc, are legal characters in Macintosh filenames
but can be difficult to work with on non-Macintosh systems
(where most Macintosh archives are stored). Since BinHex and
MacBinary store your original Macintosh filename, removing
strange characters from a BinHex'd or MacBinary'd file before
distributing will not affect the original filename. As an
example, MyFile-215.sit is a perfectly acceptable filename.
After you have created the archive and named it appropriately,
BinHex encode it (see [2.3]). Edit the resulting text file
and include a short description of the archive you want to
distribute, including any system requirements and problems.
If you include a signature, limit it to a single line.
Finally, upload the text file (if necessary) and e-mail it
to macgifts@mac.archive.umich.edu. Your subject line should
specify a suggested name and location for your submission,
eg:
To: macgifts@mac.archive.umich.edu
Subject: app/myfile-215.sit.hqx
Mailing your archive to macgifts automatically submits it
to the InfoMac archives, mac.archive.umich.edu, and the
Usenet group comp.binaries.mac.
Note: An alternate email address is macgifts@sumex-aim.stanford.edu
Thanks for complying with these guidelines.
[3.7] How can I use the programs that are posted to comp.binaries.mac?
----------------------------------------------------------------------
The files posted to comp.binaries.mac are in BinHex 4.0 format.
Long files are split into several postings that must be
concatenated IN THE PROPER ORDER (and usually with headers
and signatures removed) before converting.
First, read the man page or other documentation for your
newsreader. A little time spent here can save you a lot of time
doing repetitive tedious work later. Find out how to save an
article to a file.
Next, save all the posted articles for a given program posted to
comp.binaries.mac to a single file. Don't combine postings that
are for different programs, but do save multi-part postings to
the same file, in increasing order of part number. For example,
if you are using the UNIX newsreaders 'rn', 'trn', or something
similar:
***** 15 unread articles in comp.binaries.mac--read now? [=ynq]
2761 Great Icon Editor (part 1 of 2)
2762 Great Icon Editor (part 2 of 2)
2764 Hypercard Resource Tools
2765 Idea 1.2 (part 01 of 11)
2766 Idea 1.2 (part 02 of 11)
2767 Idea 1.2 (part 03 of 11)
2768 Idea 1.2 (part 04 of 11)
2769 Idea 1.2 (part 05 of 11)
2770 Idea 1.2 (part 06 of 11)
2771 Idea 1.2 (part 07 of 11)
2772 Idea 1.2 (part 08 of 11)
2773 Idea 1.2 (part 09 of 11)
2774 Idea 1.2 (part 10 of 11)
2775 Idea 1.2 (part 11 of 11)
What next? [npq] 2761 s iconeditor.hqx
2761 Saved to mailbox /u/joe/News/iconeditor.hqx
What next? [npq] 2762 s iconeditor.hqx
2762 Saved to mailbox /u/joe/News/iconeditor.hqx
At this point, download the file "iconeditor.hqx" (it will be
automatically placed in your "News" directory) to your Macintosh
and use a program like StuffIt Expander, DeHqx, HQXer, or Compact
Pro to convert the .hqx file to a Macintosh file.
Warning: The original BinHex utility, BinHex 4.0, has a bug
that causes it to crash on large or corrupted .hqx files. It
also requires you to strip mail-headers off of .hqx files before
decoding.
The Macintosh file you create may in fact be an archive that you
then need to unarchive with the appropriate program. See the
list of file suffixes to determine which program(s) to use.
Note: You can streamline the process by:
--> using the Unix program 'mcvert' or 'hexbin' (see [6.5]) to
convert the .hqx file to a MacBinary file on your Unix host.
Since the .hqx file is usually 30% to 40% larger than the
MacBinary file, this saves download time. These utilities
are also smart enough to handle stripping headers and
signatures, although you must still save the postings in the
proper order.
--> using one of the many utilities that exist to reorder
postings automatically before you convert them from
BinHex
--> learning enough about your newsreader program to save more
than one article at once in a particular order
--> checking out the programs: StuffIt Expander, DeHqx and HQXer
================================================================================
[4] Introduction to AppleTalk (and Apple Remote Access)
=======================================================
[4.1] What kind of hardware do I need to set up an LocalTalk network?
---------------------------------------------------------------------
Be sure you have read section [5] and understand the difference
between LocalTalk and PhoneNet. Setting up an AppleTalk network
based on either LocalTalk or PhoneNet requires purchasing a box
that connects to your Macintosh's serial (printer) port with the
appropriate mini DIN-8 or DB-9 connector and provides, in the
case of LocalTalk, two mini DIN-8 connectors for Apple's
(expensive) multiwire AppleTalk cables, or, in the case of the
less expensive PhoneNet, two standard RJ11 (modular telephone)
jacks. Both boxes look similar to Figure 4.1.1.
+-----------------+
to/from <------>| |
rest of | |<--------> to Macintosh or
network <------>| | printer
+-----------------+
Figure 4.1.1
Computers and printers should be connected serially; that is,
chain the devices in any convenient order, with either
a single AppleTalk cable (LocalTalk network) or telephone
cable (PhoneNet network) connecting neighboring machines.
Do *not* connect the ends of a LocalTalk or PhoneNet
network --- this is not a ring (eg: TokenRing) network.
It should be noted that Apple is "strongly encouraging"
new AppleTalk networks to be Ethernet-based.
[4.2] How can I change the Chooser "user" and name of my Macintosh?
-------------------------------------------------------------------
Also: Why can I no longer change the name of my hard-disk?
To change the owner and name of your Macintosh under System 7,
select "Controls Panels" from the Apple Menu and double-click
on the "Sharing Setup" Control Panel.
The Chooser "user" is the "Owner name:". Change it like any
standard edit field.
The name of your Macintosh is the "Macintosh name:".
Also on this Control Panel is a button to turn File Sharing
on and off. When File Sharing is on, you cannot change the
name of shared disks. If you are trying to change the name
of your hard disk but cannot get the name to turn into an
edit field, File Sharing is probably on. Use the Sharing
Setup Control Panel to turn File Sharing off, change your
hard disk name, and then turn File Sharing back on (unless
you have no need for it).
[4.3] What is Apple Remote Access ?
---------------------------------------
Apple Remote Access is a software package that allows you
to dial-in to an AppleTalk network (or to create an AppleTalk
network between two Macintoshes via dial-up modems) from a
remote Macintosh. Remote Access requires at minimum:
o a Macintosh (possibly connected to an AppleTalk
network) designated as the host with a dedicated
high speed modem, or a dial-in server with ARA
support
o one or more remote Macintoshes with modems
o a phone line connecting the host Macintosh with
the remote Macintosh
o copies of the Remote Access software running on the
designated host as well as on all remote machines
Once configured, connecting the remote machine to the AppleTalk
network is as simple as clicking a button. Modem control is
handled automatically (assuming one of the many included modem
scripts works with your modem; see [4.4]). Passwords and call-
back facilities are provided.
Once connected, the remote machine can use the AppleTalk
network normally. One can print remotely, send messages,
access remote filesystems, monitor network traffic, etc.
Throughput, even when using 9600 bps modems, will be
significantly lower than through a LocalTalk or PhoneNet
connection; however, except for program launching and file
copies, the added delay is small.
You CAN use slower 2400 bps modems, but you will probably not
enjoy the experience.
The University of Melbourne has developed a useful but not
well known package known as ARNS, or A Remote Network Server.
ARNS allows remote clients to use network services such as
printing and file sharing. The server can run on either a UNIX
or a Macintosh host; clients connect through an IP interface
(e.g. MacTCP, CAP). With ARNS, it is possible to use a dial-up
SLIP account to tunnel into an existing UNIX based AppleTalk
network. Servers for UNIX and MacOS can be found by anonymous
FTP from munnari.oz.au in directory mac.
[4.4] Where can I get a Remote Access script for my modem?
----------------------------------------------------------
If none of the (many) included modem scripts work with your
modem, try:
o searching the InfoMac archives for a script for your
modem; several scripts have been posted recently
o searching the database of Remote Access scripts maintained
by Apple. Use ARA to dial (512) 908-8118, and log on as
guest
o making a copy of the script that works best with
your modem (the scripts are in the Extensions Folder
which is in the Systems Folder), opening it up with
a text editor, and experimenting; this assumes you
have a copy of your modem's manual and know the
basics about the Hayes command set. If you are
succesful, post your script so others can benefit!
[4.5] How are IP packets transmitted over a LocalTalk network?
---------------------------------------------------------------
A Mac on a LocalTalk network, if that network only uses the
AppleTalk protocol, does not send and receieve IP packets. Instead,
it uses DDP (AppleTalk) packets. If the Mac is attempting
to use an AppleTalk service (for example, AppleShare file
sharing), then it will speak DDP to the Mac serving as the AppleShare
server, and that server will talk back to the Mac in DDP. All is well;
only one protocol is used.
If, on the other hand, the LocalTalk-connected Mac wants to
use IP services (for example, telnet or ftp), it must first
encapsulate its IP packets in DDP packets, and then pass those DDP
packets over the network. This encapsulation is done by MacTCP. At some
point these DDP packets must be converted into IP packets (esentially
by stripping off their AppleTalk headers) if they are to be sent over
an IP network such as the Internet. This translation is done by a
DDP-IP gateway (sometimes called a MacIP server). This DDP-IP gatway
is connected on one side to the AppleTalk network (here we use the
term "AppleTalk" because the protocol being used is AppleTalk; the
network may be a LocalTalk network, but need not be), and on the other
side to an IP network (which is eventually connected to the Internet,
we assume). In addition to converting DDP packets into IP packets, the
DDP-IP gateway converts IP packets destined to AppleTalk nodes on its
network into DDP packets. Of course, MacTCP on your Mac must decapsulate
the DDP packet and extract the IP packet, which is then passed to the
IP application (telnet, ftp, etc.) running on your Mac. The process
looks something like this:
I
n
t IP ----------- DDP ------------- IP ---------------
e------| DDP-IP |----------| MacTCP on |------| your IP |
r | Gateway | Apple- | your Mac | | application |
n ----------- Talk ------------- ---------------
e Network (telnet, ftp, ...)
t
Therefore, to use IP services on a Mac connected to a
LocalTalk network, you must use the MacTCP control panel to select a
link icon which support MacIP service (e.g. LocalTalk, EtherTalk, or
Remote Only). A pop-up menu will be added below the link icon, listing
all the zones on the AppleTalk network to which you are currently attached.
There you choose the zone in which your DDP-IP Gateway resides.
You must also configure the MacTCP IP information your Mac
appropriately. "Appropriately" means that if the DDP-IP gateway assigns
a different IP address each time IP services are requested of it, you
must select "server" addressing. If the DDP-IP gateway assigns
fixed IP addresses (i.e. each node on the AppleTalk network
has its own permanent IP address) then you should select "manual"
addressing and enter your proper IP address. You must also fill in the
Domain Name Server information as it pertains to your site. Note that
you do not have to bother with setting the default IP gateway or
subnet mask, since your Mac doesn't need to know this; it will be
sending ALL its IP traffic to the DDP-IP gateway; that gateway knows
about IP routes and subnet masks, and it handles the routing of the
packets.
In summary, the equipment you need in order to get IP services on
your LocalTalk-connected Mac are MacTCP on the Mac and a DDP-IP gateway
(which may be hardware such as a Shiva FastPath, a compatible Cisco
router, or a Cayman Gatorbox; or software, such as Apple's "Apple IP
Gateway"). The Apple IP Gateway program runs on a Macintosh and allows
any Ethernet-connected Mac to serve as a DDP/IP Gateway. The Apple IP
Gateway software can also concurrently run with ARA server, or the
AppleTalk Internet Router software.
NOTE: These days, most networked Macs are on an Ethernet network. In
this case, the transport medium is Ethernet, not LocalTalk, and the
AppleTalk packets are encapsulated in Ethernet packets before being
sent out over the Ethernet. Therefore, the DDP-IP gateway takes
Ethernet packets off the Ethernet, extracts the DDP packets,
then extracts the IP Packet, and then sends that IP packet off onto
the Internet. Likewise, the DDP-IP gateway takes IP packets destined
to nodes in its LAN off the Internet, encapsulates them in DDP,
then encapsulates them in the appropriate Ethernet headers, and then
puts them onto the Ethernet. The DDP-IP gateway can also facilitate
communication between DDP Macs and IP hosts (UNIX workstations, for
example) on the same Ethernet through an analogous conversion process.
[4.6] How can I use Apple Remote Access to access the Internet via my
Mac at work?
---------------------------------------------------------------------
First, if you have not read [4.5], then read it now. You must
understand [4.5] in order to understand the answer to this question.
The Apple Remote Access connection between your Mac at home and
your Mac at work is, in effect, a LocalTalk network; therefore, AppleTalk,
and not IP, is the protocol used over this line.
The remote (ARA) Mac is the same as the networked Mac in [4.5]. It
must be running a properly-configured MacTCP as well as the ARA client
software. Your Mac at work is not the same as the Mac in [4.5];
it needs to be running the ARA Personal Server software, but does NOT
need to be running MacTCP, since the packets it will receieve over the
telephone line are DDP packets (with IP encapsulated inside) and it
merely needs to pass these packets on to the DDP-IP gateway. The Chooser
on the remote (ARA) Mac must select the the DDP-IP gateway. The Chooser
on the office Mac does not require any particular setting.
Once this is done, you will be able to use IP services from
your Mac at home. If you want to receieve IP services for your Mac at
work, simply install MacTCP on that Mac and configure MacTCP as you
configured MacTCP on the Mac at home (this is described in [4.5]).
The situation here looks something like this:
I
n IP ----------- DDP ---------------- --------------
t-----| DDP-IP |------| ARA Personal | DDP | ARA client |
e | Gateway | ^ | Server on |-----------| on Mac at |
r ----------- | | Mac at work | telephone | home |
n | ---------------- line --------------
e AppleTalk |
t network | DDP
|
---------------
| MacTCP on |
| Mac at home |
---------------
|
| IP
|
------------------
| IP application |
| on Mac at home |
------------------
(telnet, ftp, ...)
Again, we note that your Mac at work can be connected to an Ethernet
network instead of a LocalTalk network. In this case, your office
Mac's IP packets are encapsulated in DDP and then encpauslated in
Ethernet headers before being sent over the network (and, when receiving,
the opposite takes place). [The office LAN is labeled "AppleTalk network"
in the above diagram.]
Note: There must only be one DDP-IP gateway per AppleTalk zone. Use of
more than one DDP-IP gateway in a single AppleTalk zone may result in
all gateways in that zone ceasing to function. Therefore, if you are
thinking of running the Apple IP Gateway software (mentioned in the
previous question) on your own computer, be sure to check first with your
local AppleTalk network administrator to avoid interfering with any DDP-IP
gateway which might already exist in your zone.
Thus, to connect your Mac at home to the Internet via your
Mac at work, you need the following hardware and software
o a modem on your Mac at home (at least 9600 bps modem is
o a modem on your Mac at work highly recommended here!)
o Apple Remote Access client software on your Mac at home
o Apple Remote Access Personal Server software on your Mac at
work
o MacTCP on your Mac at home
o Your office Mac must be connected to an AppleTalk network
which contains a DDP-IP gateway, and that gatway
must have a path to the Internet
[4.7] How can I use the services of my EtherTalk network and print
to my LocalTalk-only printer at the same time?
-------------------------------------------------------------------------
By default, Macs can only use AppleTalk for communication through one
network interface at a time. This means that without special hardware
or software, if you are connected to an EtherTalk network through your
Ethernet port/card and are also connected to a LocalTalk-only printer
through your LocalTalk port, you cannot use the EtherTalk network services
and print to your LocalTalk printer simultaneously. (EtherTalk is
AppleTalk datagrams encapsulated in Ethernet packets running on Ethernet
wiring, and LocalTalk wiring in this scenario is used to communicate with
your printer using AppleTalk datagrams; hence to use both services
simultaneously you would need to be communicating out of two network
interfaces using AppleTalk simultaneously.) You tell your Mac
which interface you want to use by selecting either EtherTalk or
LocalTalk from the Network Control Panel.
As Ethernet wiring becomes increasingly popular for transporting
AppleTalk datagrams, many people want to share files or print over their
EtherTalk network without losing simultaneous access to their LocalTalk-
connected printer. A number of solutions exist to solve this problem.
The simplest solution is to use software on your Mac which allows your
Mac to speak a subset of AppleTalk through its LocalTalk port, while
it continues to use the Ethernet port for the majority of its
AppleTalk traffic. These products typically only support printing, and
often to just one device. They allow your Mac to see that printer, but
no other Mac on the network can see the printer. Two products in this
category are Sonic System's PowerBridge 3.0 and the Apple LaserWriter
Bridge. Apple LaserWriter Bridge 2.0 is bundled free with Apple's Network
Installer 1.5 (due first quarter 1995).
If you want to share your LocalTalk printer with other Macs on your
EtherTalk network, you need true bridging software. This turns your Mac
into a LocalTalk/Ethernet bridge, passing AppleTalk packets between
the two interfaces. This allows users of the EtherTalk network to see
and use your LocalTalk printer if your Mac is turned on and working
properly. Such bridging software might also support services beyond
printing, allowing Macs on your EtherTalk network to see any LocalTalk
devices connected to the bridging Mac (including any Macs on a LocalTalk
network connected to the bridging Mac). It typically does not provide a
MacIP server (to encapsulate and decapsulate TCP/IP). Three products in
this category are Farallon PowerPath, Farallon LocalPath, and Apple
LocalTalk Bridge 1.0 (the last item is not available yet.)
For faster and possibly more reliable service than software bridging,
you need a LocalTalk/Ethernet hardware bridge. This bridge performs
the same service as the software bridge described the above paragraph,
passing AppleTalk packets between its Ethernet and LocalTalk interfaces.
It allows Macs on the EtherTalk network to see and use any LocalTalk devices
attached to the LocalTalk network connected to the bridge. It typically
does not provide a MacIP server. Hardware devices in this category include
Dayna EtherPrint, Sonic MicroPrint, Asante AsantePrint, Farallon EtherWave
MultiPrinter Adapter, and Farallon EtherWave LocalTalk Printer Adapter.
The final option is a LocalTalk/Ethernet router, which routes packets
between a LocalTalk network and an Ethernet network, and converts packets
between EtherTalk and plain AppleTalk as needed. A product in this
category is the Shiva FastPath.
[4.8] Is it possible to use AppleTalk over a TCP/IP network?
------------------------------------------------------------
Yes, you can use AppleTalk over a TCP/IP network by encapsulating
AppleTalk in IP. You need special software on your Mac to do this;
essentially it is just providing AppleTalk with yet another link
access protocol. But since any of the AppleTalk devices you want to
talk to on your network aren't going to speak AppleTalk in IP, you
need a gateway somewhere on the IP network that will receive
your AppleTalk-in-IP packets, decapsulate them, and then put your
AppleTalk packets back out on the network. And it must do the
reverse, of course, for AppleTalk packets on their way to you.
(Formally, this is known as IPTalk or UDPTalk, or tunnelling AppleTalk
over IP. Some sites do this because they have chosen not to permit
AppleTalk itself as a protocol on their network.)
There are one or more implementations of Mac IPTalk clients and UNIX
IPTalk gateways available from the usual ftp sites. Two places to
look are ftp://ftp.shiva.com/unsupported/iptalk/iptalk.sit.hqx and
ftp://pop.lbl.gov/lblnet/{IPTalk,IPTalkDoc}.sea.hqx
Another approach, which has the same goal but in fact is done quite
differently, is ARNS. It too, is an approach involving encapsulating
AppleTalk in something else (*not* IP; they use their own approach).
There's a Mac ARNS client that will encapsulate AppleTalk into a
datastream that is unwrapped by a UNIX ARNS program that you run from
a UNIX shell after logging into a UNIX system; it passes the data
to a daemon running on the same (or other) UNIX system or Mac system
(via IP), which then does that actually gatewaying of the AppleTalk on
to the Ethernet. There's also a Mac ARNS client that will work over a
PPP link, and one that will work with ARA. The various ARNS clients
and servers are available from the usual ftp sites.
If you are accessing a TCP/IP network via PPP dialup, and you have a
PPP server which supports PPP/AppleTalk, then you don't need to encapsulate
your AppleTalk packets in IP. The PPP protocol is itself designed to
transport different protocols, including IP and Appletalk. You must, however,
not only be dialing into a PPP server which supports PPP/AppleTalk, but you
also must be using a PPP/AppleTalk-capable LAP driver. MacPPP is not
PPP/AppleTalk-capable. The InterCon/Tribe/Pacer PPP drivers are the only
available PPP LAP clients which will handle PPP/AppleTalk.
================================================================================
[5] Networking, MacTCP, Telnet, SLIP, PPP
==========================================
[5.1] What is MacTCP and what kind of hardware and software do I need to use it?
--------------------------------------------------------------------------------
MacTCP is Apple's implementation of the Defense Advanced Research
Projects Agency (DARPA) TCP/IP Protocols (see [5.2]). MacTCP's
software interface is a Control Panel, which means that it loads
when your Macintosh boots. Under System 6.0.X, MacTCP will reside
in the System Folder; under System 7.0, it should be placed in
the Control Panels Folder.
MacTCP accomplishes two important tasks: it is a tool that lets
programmers who wish to develop TCP/IP based applications do
so without "reinventing the wheel". By providing a standard
interface to TCP/IP network hardware, MacTCP also makes it
possible for more than one TCP/IP based application to run on a
Macintosh at any one time. For example, you can simultaneously
use a Telnet program, an FTP program, and share a filesystem
via NFS when you use MacTCP to provide the interface to your
TCP/IP network.
The latest version (6/95) of MacTCP is MacTCP 2.0.6. The last
pre-2.0 version, MacTCP 1.1.1, remains in common use. Both
versions require a Macintosh Plus or later CPU, System 6.0.5
or better, a direct connection to an Ethernet or TokenRing
network (typically a Ethernet or TokenRing card), a SLIP or
PPP dialup connection, or a connection to a LocalTalk network
with a DDP-IP router such as a Shiva FastPath, Cayman Gatorbox,
Webster Multigate, or Compatible EtherRoute TCP.
An update to MacTCP version 2.0.6 is available as part of the
System 7.5 update available at ftp://ftp.support.apple.com/
pub/apple_sw_updates/US/Macintosh/System Software/System_7.5_Update_1.0
If you are using System 7.1, you should be using MacTCP 2.0.6 or
higher, or at the very least 1.1.1. Note: There are known bugs
with 2.0; Apple recommends upgrading. Upgraders for various version
are available at various FTP sites, including Info-Mac sites
and seeding.apple.com.
Macintosh OS versions 7.5 and later include MacTCP as part of
the standard operating system.
As indicated above, MacTCP is an Apple product available from
APDA; product numbers and official names are listed below (8/93).
Note that MacTCP 2.0 is known by "Connection for Macintosh".
M8113Z/A TCP/IP Connection for Macintosh 59.00
M8114Z/A TCP/IP Administration for Macintosh 199.00
Individuals interested in obtaining MacTCP may wish to investigate
Adam Engst's book, "Internet Starter Kit for Macintosh". Published
by Hayden and typically selling for $30 (or less), it includes
MacTCP and other software useful for accessing the Internet from
your Macintosh. It's ISBN number is 1-56830-064-6.
Many universities have campus site licenses for MacTCP; your site
may also have such an arrangement --- check before buying. It
is also now possible to buy MacTCP from mail-order companies;
check around, and you may find a better price than APDA.
Annual site licenses pricing (7/93): .edu .com
1 - 2000 Macintosh CPUs $1000 $3000
2001 - 5000 $1500 $4500
5000 - unlimited $2500 $7500
NOTE: MacTCP is now bundled with Apple's System 7.5.
For more detailed information regarding setting up a Macintosh
to connect to a TCP/IP network using MacTCP, see Eric Behr's
report on MacTCP which is archived at the various FTP sites
as mac-tcp-info.txt. This report provides a lot of useful
information for first-time Macintosh networking administrators.
According to the document itself,
"The newest release of these notes can be obtained by
anonymous ftp to ftp.math.niu.edu (the text file
/pub/mac/doc/mactcp.txt), or by gopher to gopher.math.niu.edu
("Help Files/Help For Macintosh Users"), or as
http://www.math.niu.edu/~behr/docs/mactcp.html. The HTML
version is usually updated first and may be more accurate."
Some related information is also available at
ftp://ftp.math.niu.edu/pub/mac/doc/
From the "obscure MacTCP configuration suggestions" file
(submitted by Larry W. Virden <lvirden@cas.org>):
We have a series of machines known only by internal hosts file as
well as one machine which acts as a firewall/gateway to DNS for
external machines. We had a hosts file in the System Folder,
listed the gateway machine in the MacTCP 2.0.4 control panel, and
marked that DNS entry as the default.
We found that users could get to external machines, but not to the
machines in the hosts file. If they unmarked the DNS entry as the
default, then they could get to the internal hosts, but not to the
external machines.
To resolve the problem, we had to add a second DNS host, with the name of
. and the same IP address as our gateway, and then not mark either as the
default name server. When we did this, MacTCP would go to the hosts file
first, and if the address is not found there, it goes on to the gateway
for the external hosts.
[5.2] What are AppleTalk, LocalTalk, Ethernet, EtherTalk, TCP/IP, etc?
----------------------------------------------------------------------
When attempting to describe networking terms, a distinction
should be drawn between networking _protocols_ (such as
AppleTalk and TCP/IP) and networking _hardware_ (such as
LocalTalk, Ethernet, and TokenRing). In most cases, a specific
protocol can be used over more than one hardware medium.
In order to help understand the interaction of these disparate
parts in a real-world network, we can adopt the useful analogy
of multi-layer cake with the physical wire at the very bottom
and the software which you are running at the very top.
Thus, we can think of LocalTalk, Ethernet and TokenRing as being
the layers at the bottom, AppleTalk and TCP/IP in the middle and
programs like NCSA Telnet, NFS/Share and MacX at the top.
The following terms describe protocols (software descriptions)
common to the Macintosh networking world:
* AppleTalk: A proprietary suite of protocols developed by Apple
Computer, Inc. that provides for near-transparent network
connections between Macintosh computers. However, within the
last few years AppleTalk has been ported to operating systems
other than the Macintosh OS, including UNIX, VMS and DOS.
Questions about the AppleTalk protocol are probably best posed
in the newsgroup comp.protocols.appletalk .
* TCP/IP: A suite of protocols developed by the Defense Advanced
Research Projects Agency (DARPA) whose purpose is multi-platform
connectivity. TCP/IP drivers are available for almost all of the
computer platforms in use today, including micros, minis, main-
frames and supercomputers. TCP/IP stands for Transmission Control
Protocol/Internet Protocol, because these are the two most widely
used protocols in the suite. However, TCP/IP includes the User
Datagram Protocol (UDP), Address Resolution Protocol (ARP),
Reverse Address Resolution Protocol (RARP) and others.
* EtherTalk: The driver which allows AppleTalk protocols to be
transported by Ethernet.
* TokenTalk: The driver which allows AppleTalk protocols to be
transported over IBM TokenRing networks.
The following terms describe hardware (the physical link such
as the wire(s) connecting computers) common to the Macintosh
networking world:
* LocalTalk: One type of hardware over which AppleTalk protocols
can be transported. LocalTalk has a throughput of 230.4 Kilobits
per second, or roughly a quarter of a Megabit per second.
* PhoneNet: Another type of hardware commonly used to transport
AppleTalk packets. PhoneNet mates LocalTalk hardware with
ordinary (unused) telephone wire. PhoneNet is probably the
cheapest way to connect widely separated Macintosh computers
within a single building.
* Ethernet: A network medium over which AppleTalk, TCP/IP and
other protocols travel, often simultaneously. Ethernet's maximum
throughput is 10 Mbps. Competing successors offer 100 Mbps.
* TokenRing: A network medium developed (and patented) by IBM
based on a topology of a ring of nodes connected serially by a
single cable. Each node, or computer, speaks on the cable only
when it has posession of a token. TokenRing technology can
demonstrate throughputs of ranging from 4 to 16 Megabits per
second.
[5.3] What is Telnet, and is there a Telnet program for the Macintosh?
----------------------------------------------------------------------
Telnet is a high speed terminal connection protocol designed
with TCP/IP in mind. A Telnet program allows you to connect
to computers that accept Telnet sessions (such as UNIX boxes)
with interactive full-screen console input and output
capabilities in mind.
There are several Telnet programs for the Macintosh. The first
and most widely used is NCSA Telnet, which is free and can be
found via anonymous FTP from ftp.ncsa.uiuc.edu (as well as
elsewhere). The latest version is 2.6 and supports TEK 4105
graphics, provides both an FTP server *and* client, and can do
session logging. Versions 2.6 and later require MacTCP. That
version also adds a completely new configuration system.
Comet, the Cornell Macintosh Terminal Emulator, is a
Freeware communications program which offers multiple VT102 and
IBM 3278 emulator Telnet sessions (using MacTCP) as well as
serial VT102 connections. A TFTP server is provided for TCP/IP
file transfer; in addition the "ft3270" file transfer protocol
supports file transfer with IBM VM hosts over Telnet and serial
connections. Comet 3.0 supports scrollbars and a ".edit" TextEdit
window for each session. Comet is available via anonymous FTP from the
pub/mac/comm/comet/ directory of ftp.cit.cornell.edu.
Hytelnet is a Telnet program available for various personal
computers including the Macintosh. The Macintosh version is
based upon Hypercard 2.x. Contact Charles Burchill at
<burchil@ccu.umanitoba.ca> for more information about Hytelnet.
InterCon Systems has a fully-functional Telnet Connection Tool
for use with the CTB). InterCon's TCP/Connect II includes
Telnet and FTP facilities (and a host of other features).
VersaTerm 5.0.4 ships with a Telnet Connection Tool (in
addition to MacTCP). However, this tool seems to be intended
to be used only with VersaTerm and does not support all
Telnet features.
Advanced Software Concepts distributes 5PM with MacTCP, a
Telnet Connection Tool and a FTP server. 5PM includes a
HyperTalk-like scripting engine and allows the user to create
"palettes" which are similar to HyperCard cards.
Stanford University Networking Systems has distributed a package
known as SU-Mac/IP that includes Telnet, FTP, tn3270, printing
facilities and other MacTCP based capabilities. The package
can be licensed *ONLY* by "degree-granting institutions of
higher education". For information, either send e-mail to
macip@jessica.stanford.edu or call [USA] (415) 723-3909.
Walker, Richer, & Quinn, Inc., offer a trio of HP and VT terminal
emulation products for the Macintosh. Reflection 1+, 2+, and 4+
include a fast proprietary file transfer tool and a connection tool
(NS Connection) which implements HP's NS/VT terminal communications
protocol. Reflection 1+ emulates the HP 2392A, 700/92, and 700/94
text terminals, the HP 2393A and 2623A monochrome graphics terminals,
and the VT52, VT102, and VT220 HP ANSI terminals. Reflection 2+
emulates the Digital VT52, VT102, VT220, and VT320 terminals.
Reflection 4+ emulates the Digital VT52, VT102, VT220, and VT320
terminals plus ReGIS and Sixel graphics. According to the
company's sales information,
All Refletion products include multiple terminal and file
transfer sessions, each in a separate window; a macro
language; and support for connection and file transfer tools.
Tools supplied include telnet, serial, LAT, XMODEM, Kermit,
and WRQ, a proprietary high-speed transfer protocol with
host directory support for HP, DEC, and UNIX hosts. The
Reflection emulators support the Communications Toolbox
connection tools and file transfer tools. The Communications
Toolbox, MacTCP, and the Apple Basic Connectivity Set are
included (serial, modem, ADSP, LAT, and XMODEM tools.)
WRQ provides the following additional tools: (file transfer)
WRQ, Kermit WRQ, Old-WRQ, XMODEM WRQ, ZMODEM WRQ;
(connection) serial WRQ, telnet, NLAT (Netware for LAT).
Complete, graphical keyboard mapping for host key sequences,
menus, command macros, and Reflection Command Language
scripts. Full support for 80 & 132 columns, 24-144 rows,
resizable fonts, double high double wide characters,
international character sets, dynamically redefinable
character sets, character attributes, and color. Includes
Reflection Command Language, a complete, BASIC-like
scripting language.
WRQ file transfer protocol provides host directory support,
drag and drop, wildcard transfers, MacBinary, retention
of host file attributes, data and time filters, and speeds
of up to 300 kilobytes per second over Ethernet. Host file
transfer programs for VAX, Alpha, UNIX, and HP3000 are
provided with each copy of Reflection. A 'bootstrap' script
uploads the host transfer programs directly from the Macintosh.
Companion products for DOS and Microsoft Windows are available.
It should also be mentioned that any CTB-based Mac
telecommunications program can use the telnet protocol if you
also have the Telnet Tool.
[5.4] Is there a FTP (client/server) program for the Macintosh?
---------------------------------------------------------------
Yes, you can choose from freeware, shareware and payware
varieties:
* NCSA Telnet (see [5.3]) includes both FTP client and server
capabilities.
* Fetch 2.1.2 (from Dartmouth) is a free FTP client application
for educational institutions. Otherwise, it requires a license.
Fetch provides a more intuitive interface than the conventional
text-based mechanism.
* FTPd, $10, by Peter Lewis <peter@cujo.curtin.edu.au>, is a
high-quality shareware FTP server with many features:
o Multiple simultaneous users.
o Uses System 7 Users & Groups to define users and passwords
o Supports BinHex and MacBinary transfers, including the MACB
command.
o Allows login to other AppleShare servers on the local
network.
o Allows different formats of a file to be fetched.
o Pattern matching in change directory command.
o Individual initial directory for any user.
o FTP site descriptions sent after login.
o Directory descriptions sent after CD command.
o Supports the CatSearch feature to allow very fast volume
wide searches.
* HyperFTP, a Hypercard-based FTP client.
* XferIt, by Steve Falkenburg, a shareware FTP client.
* VersaTerm 5.0.4 also ships with an FTP CTB Tool.
* Advanced Software Concepts sells FTPShare, a commercial FTP
server product and has posted a demo to InfoMac. Main features
(according to authors) are:
o Operates very similar to System 7 FileSharing.
o Also works under System 6.
o Quite fast.
* Pathway Access Macintosh from The Wollongong Group, Inc. offers
both FTP client and FTP server, with a graphical user interface
for both. The product also includes a large suite of terminal
emulations for telnet connections, a script compiler, and a print
server.
* Walker, Richer, & Quinn, Inc. offers the Reflection series of
terminal emulators which include support for file transfer. See
the description of this product in [5.3].
[5.5] What are SLIP, CSLIP and PPP?
-------------------------------------
SLIP stands for Serial Line Internet Protocol. SLIP is a
"non-standard" for framing IP packets and shipping them over
a serial line (e.g. a cable, or a pair of modems), thus
allowing a home machine to dial up and become part of the
Internet. Effectively, SLIP turns a serial port into a logical
Ethernet port.
Many workstations and terminal servers can support SLIP. On
the Macintosh side, several vendors offer SLIP modules for
MacTCP. (These vendors and products are summarized below).
Macintosh software which communicates with the outside world
via MacTCP will continue to work over SLIP, albeit somewhat
more slowly due to the relatively low bandwidth of modem
connections.
CSLIP stands for Compressed SLIP. CSLIP reduces the size of
the headers in IP packets by eliminating a certain amount of
redundancy. This improves interactive performance.
PPP stands for Point-to-Point Protocol. PPP can support both
synchronous and asynchronous connections and protocols that
are not IP-based (such as AppleTalk). It provides specifications
for error detection, feature negotiation, escaping control
characters, etc. PPP is becoming more and more popular,
especially as MacPPP, a MacTCP extension available via anonymous
FTP from merit.edu in pub/ppp, has matured into a stable and
viable alternative to the various available MacTCP SLIP LAPs.
Although SLIP continues to be more prevalent than PPP, PPP will
become more prevalent in the future. For more information on PPP,
consult the FAQ for the newsgroup comp.protocols.ppp.
Recently, several vendors have provided SLIP LAPs for MacTCP.
What is a "MacTCP SLIP LAP"? To quote Steve Dorner, "It's an
extension that allows MacTCP to work over a phone line, allowing
you to use any MacTCP application over your modem, if you have
the right dialins." LAP stands for Link Access Protocol. You
choose the LAP you want to use via the MacTCP Control Panel.
Currently, the following SLIP products for the Macintosh are
readily available:
o MacSLIP from Hyde Park Software is a MacTCP extension that
supports SLIP and CSLIP and a scripting language for
session. Individual copies sell for $49.95.
Contact: info@hydepark.com, [USA] (800) 531-5170. Sales
and support are handled by TriSoft.
Reports of transfer rates as high as 1500 bytes/sec have
been posted to comp.sys.mac.comm by users of MacSLIP on
V.42bis 9600 bps modems. Transfer rates as high as 3 KB/sec
are possible through a 38400 bps connection.
o InterCon Systems is shipping a MacTCP extension with their
networking product (TCP/Connect II), and as a separate
package (InterSLIP).
HOWEVER, InterCon has graciously made InterSLIP available
to Internet users for FREE. You can FTP InterSLIP from
ftp.intercon.com in InterCon/sales.
Demonstration versions of various InterCon products are also
available at this FTP address.
Contact: sales@intercon.com, [USA] (703) 709 9890
o Synergy Software offers a CSLIP MacTCP extension with
its VersaTerm/VersaTerm-PRO packages. If you already own
Versaterm, SLIP is a $20 upgrade. If you buy the complete
VersaTerm 5.0.4 package, you will also get an
FTP server and client, a Telnet connection tool, and MacTCP.
Performance is comparable to that of MacSLIP.
Contact: [USA] (215) 779 0522
For a review of Macintosh SLIP products, see the November 16, 1992
issue of "Open Systems Today". Benchmarks are included.
Currently, the following PPP products for the Macintosh are
readily available:
o IP-only
+ Merit/Umich PPP
o IP and AppleTalk
+ InterPPP (from InterCon; see contact information above
or at the end of the FAQ)
+ TribePPP (included with Tribe PPP server)
+ PacerPPP (included with PacerTerm software)
Note: If you are using MacTCP over a dialup SLIP or PPP link,
MacTCP 2.0.4 or later is recommended. Previous versions have
an annoying retransmission problem that can slow down serial
connections. If you must use v1.1.1, get the MacTCP-Patch
program; it's available as mac/misc/update/mactcppatch.cpt.hqx
at mac.archive.umich.edu.
[5.6] What is the difference between SLIP and PPP?
--------------------------------------------------
If SLIP and PPP both allow a TCP/IP connection over a phone line,
which one should I choose? What follows is a synopsis of the reasons
that PPP is better than SLIP.
o PPP supports link level error detection insuring a more robust
connection than SLIP.
o PPP allows characters like XON and XOFF and others to be
"escaped" so that the regular group of modems that are used for
terminal emulation (and need software flow control) can be used
for PPP.
o PPP negotiates all of the settings that can make the connection
unsuccessful, SLIP requires you to know the settings before
attempting the connection.
For example: PPP will compress headers if the server allows it.
With SLIP you would have to know this and run CSLIP not SLIP.
SLIP will fail to connect to a CSLIP server and CSLIP will fail
attempting a connection to a SLIP server.
o If the PPP server supports the Password Authentication Protocol,
a connection can be mode without any user scripting. You will
be prompted for a username and password if it is not entered.
And a stored password can be encrypted so it is not be visible
to prying eyes (as done by MacPPP and InterPPP).
o PPP has been blessed by the Internet Engineering Task Force and
the Internet Activities Board as a standards-track protocol.
SLIP is a self-described "nonstandard".
o SLIP only supports IP (Internet Protocol), PPP supports not only
IP, but it can (and will soon) support AppleTalk, IPX (Novel),
LAT (DEC's Local Area Transport), and others are planned. This
makes it a protocol for the future.
Isn't SLIP faster than PPP?
PPP has more overhead than SLIP in the protocol because of error
correction in the link layer. But because PPP allows larger
packet sizes, the difference can be negated. In fact, file
transfers over a PPP connection to a Telebit NetBlazer have been
reported to be faster than a CSLIP connection to the same device.
There are significant savings to been gained when a file doesn't
have to be transferred a second time because the error-free modem
connection wasn't.
Doesn't a PPP connection take longer to establish a connection?
Since PPP negotiates the settings on startup, the initial
connection takes longer. But the additional 3 seconds is
dwarfed by the 24 seconds needed by the phone company and modems.
Is there a commercial version of PPP?
InterCon Systems is shipping a MacTCP PPP LAP called InterPPP.
InterPPP actually does SLIP, CSLIP, *and* PPP.
See section [5.5] for InterCon Systems contact information.
Where can I find additional information about PPP?
Morning Star Technologies, a commercial PPP server developer has
more information about PPP in the following location:
ftp://ftp.morningstar.com//pub/papers/
The files are as follows:
o sug91-cheapIP.ps.Z
A 14 page PostScript document titled "Low-Cost IP Connectivity"
by Robert A. Sutterfield. This contains all of the above
information and more, includes figures and references.
o ppp-white-paper.ps.Z
A 4 page PostScript document titled "PPP White Paper" which
contains the same information as the above document in a compact
format.
o sug91-cheapIP-slides.shar.Z
Slides for a presentation of the above "Low-Cost IP Connectivity"
paper. Duplicates of the figures in the same paper and no text
explanations suggests this is of no interest.
o ppp.faq-3.17
The FAQ for the comp.protocols.ppp newsgroup.
o The official SLIP RFC (Request For Comments) can be found as:
ftp://ns.ripe.net/rfc/rfc1055.txt
o The official TCP Header compression RFC can be found as:
ftp://ns.ripe.net/rfc/rfc1144.txt
o The official PPP RFC's can be found as:
ftp://ns.ripe.net/rfc/rfc1331.txt
ftp://ns.ripe.net/rfc/rfc1332.txt
ftp://ns.ripe.net/rfc/rfc1333.txt
ftp://ns.ripe.net/rfc/rfc1334.txt
[5.7] MacPPP Frequently Asked Questions
---------------------------------------
For a description of MacPPP, see sections 5.5 and 5.6 of this
document. The current version of MacPPP is 2.0.1. The file
'macppp.txt' contains a detailed description of how to configure
MacPPP and should be read before you attempt to install it.
'macppp.txt' is available from wherever you got MacPPP.
* How do I configure MacPPP?
First read the file 'macppp.txt' and your MacTCP documentation.
'macppp.txt' will tell you everything you need to know to get
MacPPP working. There are some further suggestions and answers
below.
* Should I fill in the IP address field in MacTCP?
No.
* How should I set the 'Obtain address' setting for MacTCP?
Set this to 'server'. If you need to specify a fixed IP address
then put it in the 'local' field of the IPCP dialogue (in the
Config PPP Control Panel).
* Do I need to set the Gateway Address in MacTCP?
No. MacPPP will set this at connect time.
* Do I need to set the Subnet Mask in MacTCP?
No. MacPPP will supply MacTCP with the correct subnet mask at
connect time.
* Do I need to set the Domain Name Servers list in MacTCP?
Yes. You will need to get this information from your system
administrator or service provider. See section 5.8 of this
document for a description of how MacTCP uses the Domain Name
Server entries.
* Which Port Speed setting should I use for MacPPP?
If you are using a modern modem (e.g. V.32bis, V.34) then the
best setting is likely to be 57,600. This will give you the
best possible throughput of data. Older 68000 based machines
can have problems with speeds over 19,200. Problems with MacPPP
can sometimes be related to the port speed. If you are having
difficulties, it is a good idea to reduce the Port Speed to,
say, 19,200. When you have MacPPP working reliably, you can
gradually increase the Port Speed. If you encounter problems
again, go back to the fastest setting that works.
* Which Flow Control setting should I use?
If you have a full hardware handshaking cable (see section 1.2
of this document), and a modem that supports it (most modern
modems will), set this to 'CTS & RTS (DTR)'.
You must ensure that your modem is configured to use the
handshaking method you specified in MacPPP. So, for instance,
if you selected CTS & RTS handshaking, check that your modem
will default to CTS & RTS handshake at power on - if it does
not, then enable CTS & RTS in your modem init string. Also, the
modem must be set for 'DTR override' - if this is not part of
the power-on default, then you should enable DTR override in your
initialization string.
NOTE: The 'macppp.txt' file states that MacPPP does not support
RTS flow control. This is out of date. Version 2.0.1 of MacPPP
does support RTS.
* What modem initialization string should I use?
This will depend on which modem you have. Consult your modem
manual or local systems administrator for advice. You must ensure
that the modem is configured for the Flow Control option you
have selected in Config PPP and that DTR is overridden
(probabaly &D0). If the settings you need are your modem's
power-on defaults, then you can use 'ATZ' as a modem init;
otherwise, you must specify the relevant options explicitly in
the initializationnit string.
* Should I specify my username/password in the Authentication
Dialogue box?
The Authentication Dialogue box is only for use if you are
connecting to a PPP server that supports PAP. Many PPP servers
do not support PAP. If setting your username and password in the
Authentication Dialogue box does not result in a successful
login, and you are sure that the information is correct, and you
have ruled out any other problems, then you should not use this
dialogue; its fields must be left blank. In this case use
the Connection Script dialogue to build a script which includes
your username and password. If you do not know whether your PPP
server supports PAP check, with your service provider or System
administrator.
* Do I need to specify a connection script?
If you are connecting to a PPP server which does not support
PAP, then you must specify a connection script rather than using
the Authentication Dialogue box (see above). The connection
script must include your username and password. If you want to
"watch what happens" in order to develop a connection script,
then check the Terminal Window option on the Config PPP control
panel. Note, however, that if the Terminal Window box is checked,
MacPPP will ignore your modem initialization string and telephone
number. You will have to issue the modem commands by hand to
establish your connection. You may need to include a command to
start PPP at the remote end (this often happens automatically) -
if you need to, put this command at then end of your script.
* Do I need to change the LCP and IPCP Options Dialogue Boxes?
It is very unlikely that you will need to change these
settings. The default values should work, the exception being
for fixed IP address (see below).
* I have a fixed IP address, how do I set this in MacPPP?
Many people will not need to set their IP address explicitly;
the local terminal server will assign this for then (even if they
have a fixed address). If you do need to specify this, then put
it in the 'local' field of the IPCP dialogue box (from the
Config Server window). If you leave the local field set to
'0.0.0.0' then MacPPP will get your address from the remote PPP
server if it can. In the 'Obtain Address' section of the MacTCP
control panel choose 'server'.
* I have a fixed address; should I select Manual Addressing in
MacTCP?
No. Specify your fixed address as described in the paragraph
above. Although you could choose manual addressing in MacTCP,
using server addresses makes the configuration simpler and
also allows you to have setups for more than one PPP server /
network. With server addressing, MacTCP will ask MacPPP for your
IP address at connect time. This is done with PPP's IPCP
protocol which allows the server to pass the address to MacPPP.
If you have a fixed address, you will be assigned that address
every time you connect.
* Can I control MacPPP using Apple Script?
The Config PPP control panel itself is not Apple Scriptable.
However, the shareware OSAX 'macppp_control' allows for some
scripting. It is available from the info-mac archives and other
anonymous FTP sites. It will let you open and close a connection
and see if a connection is open.
* How do I make a MacPPP Connection Script pause?
You can build a pause into the connection script using the '\d'
special character in an out string. '\d' represents a 1 second
pause. If you need a 5 second pause use '\d\d\d\d\d'. Details
of this and other special characters can be found in the
'macppp.txt' file that comes with MacPPP.
* MacPPP drops the line after a few minutes. What's wrong?
This phenomena has a number of causes.
1) One cause is not setting your modem for DTR override when
using 'CTS & RTS (DTR)' or 'RTS (DTR) Only' Flow Control. Mac
hardware handshaking cables have the hardware line from the Mac
wired to both the RTS and DTR lines of the modem (see section
1.2 of this document for wiring diagrams). This means that when
the Mac drops its handshake line to stop the flow of data from
the modem, both RTS & DTR are dropped at the modem end.
Dropping the modem's RTS line is fine because that stops the
flow of data to the machine (until the machine is ready, whence
the line is raised again and the flow of data resumes). However,
if DTR is dropped, the modem will hang up. To avoid this,
configure the modem for 'DTR override' by including the appropriate
setting in your modem initialization string.
2) If you have selected an Idle Timeout, then MacPPP will seek
to drop the connection when there has been no traffic for the
period you have specified. Normally a dialogue box will appear,
but, if you have checked the 'Quiet Mode' box in Config PPP, the
disconnection will occur silently.
3) Some PPP servers will cut the link after a number of minutes
of inactivity. This is to stop you tying up a network line if
you are not making use of it. If you want to defeat this you
will need to generate some network activity every few minutes.
* Should I use Hard or Soft Close to terminate my PPP session?
If you choose 'Soft Close' and any TCP application that you are
running makes a TCP call, the PPP link will be automatically
re-established, i.e. MacPPP will dial your provider. Also,
after long periods of inactivity, MacTCP will make a request (on
it's own without any prompting from you or an app) which will
cause MacPPP to re-connect.
If you choose 'hard close' then the link will not be
re-establishsed, even on request from an application, until you
manually reconnect using the 'open' button.
Note that if your session is terminated by an Idle Timeout, the
action is equivalent to a 'Soft Close'.
* When I have closed MacPPP and leave my Mac for a long period
of time, I often return to find that MacPPP has attempted to
reconnect. How do I stop this?
Close MacPPP using 'Hard Close'. For an explanation, see above.
* How do I make MacPPP disconnect after a period of inactivity?
Set the 'Idle Timeout' to the desired interval.
Check the 'Quiet Mode' box.
* I am using the Express Modem Tool and my system freezes when I
shutdown or restart. How do I stop this from happening?
Make sure that the 'Hangup on Close' box is unchecked. If this
option is enabled, MacPPP installs a shutdown task to hangup the
modem on restart or shutdown. The Express Modem software gets
unloaded before the shutdown tasks are executed, hence the
problem.
[5.8] How does MacTCP resolve names into IP addresses?
------------------------------------------------------
If you are having problems configuring MacTCP to use dynamic
Domain Name Service entries, the following empirical description
of the behavoir of MacTCP's name resolution protocol may be
useful.
The description assumes some familiarity with IP addressing.
Step 1. Expand the target name.
If the target name contains a ".", the target name is the expanded
target name. Otherwise, prepend the name to the domain marked with
the "Default" button in the MacTCP control panel. The
concatenation of the name and this domain becomes the expanded
target name. Proceed to Step 2.
Examples:
Assume "slcs.slb.com" is the default domain for MacTCP.
"valhalla" expands to "valhalla.slcs.slb.com".
"cayman.com" expands to "cayman.com".
"apple." expands to "apple."
Step 2. Check the Hosts file in the System Folder of this Macintosh.
If there is an exact match between the expanded target name from
Step 1 and a name in the Hosts file, the corresponding IP address
from the first such match in the Hosts file is the target IP address;
otherwise proceed to Step 3. Trailing "." characters on either the
expanded target name or Hosts file name are ignored for this test.
Examples:
Assume "slcs.slb.com" is the default domain for MacTCP.
"linus" expands and matches "linus.slcs.slb.com" in Hosts.
"apple." matches "apple" in Hosts.
"apple" expands and does *not* match "apple" in Hosts.
Step 3. Find the domains that contain the expanded name.
Search through the domains from the MacTCP control panel entries,
and build a list of the domains that contain the expanded target
name. A domain contains the expanded target name if the domain is
a final string of the expanded target name. A "." by itself in the
MacTCP control panel is a domain containing any expanded target
name. The default domain is always added as the last domain of
the list, whether it contains the expanded target name or not.
Proceed to Step 4.
Examples:
Assume "slcs.slb.com" is the default domain for MacTCP.
"valhalla" is expanded and contained in domain "slcs.slb.com".
"apple." is *not* contained in domain "slcs.slb.com".
"apple" is expanded and contained in domain "slb.com".
"anyhost" is contained in domain ".".
Step 4. Consult the name servers of the containing domains.
Consult the Domain Name Servers, in the order found, based on the
corresponding IP addresses from their entries in the MacTCP control
panel. The servers are given the expanded target name to translate.
If a MacTCP is unable to contact a server, or if the server returns
a non-authoritative negative reply, the next server in line is tried.
Otherwise, the result from the server just contacted, either a
successful translation, or an authoritative "unable to resolve", is
the final result.
[5.9] Is there a version of traceroute available for the Mac?
-------------------------------------------------------------
Yes. MacTraceroute is available from your local Info-Mac
archive. To use it with Ethernet-connected Macs, you
must also pick up a copy of the "Traceroute Ethernet
LAP." MacTraceroute also works with Hyde Park's
MacSLIP. Currently, MacTraceroute does _not_ work
with InterSLIP, InterPPP, MacPPP, or any other MacTCP
LAP.
[5.10] What Domain Name Server programs are available for the Mac?
------------------------------------------------------------------
Currently the only DNS server available for the Mac is
MacDNS. Since this program is still under development, its
exact features are constantly changing. You can find out
the project's current status by visiting the MacDNS home page
at http://josaiah.sewanee.edu/macdns/macdnsInfo.html
You can FTP MacDNS from ftp://exeter.sewanee.edu/dist/MacDNS
================================================================================
[6] MacX and Other Ways to Interface With UNIX
==============================================
[6.1] Can I run X-Windows on my Mac?
------------------------------------
Yes. For Macintosh OS users (not using A/UX), two possibilities
exist.
MacX is an X-Windows server for the Macintosh, developed by
Apple. With MacX running, your Macintosh can serve as a display
server for any X-Windows client program (such as xterm, xbiff,
etc). The client programs must be running on a separate
machine running UNIX (unless you are also running A/UX, Apple's
brand of UNIX for the Macintosh).
MacX's technical capabilities, as described by Alan Mimms
in "X for the rest of us" (2/91) and paraphrased in the FAQ
for comp.windows.x are as follows:
MacX runs on MacPlus or newer machines with >= 2MB of memory
and system software 6.0.4 or later. Version 1.2 is fully
X11R4-based. It supports full ICCCM-compatible cut and paste
of text AND graphics between the Macintosh and X11 worlds,
the SHAPE extension (including SHAPEd windows on the Macintosh
desktop), an optional built-in ICCCM-compliant window manager,
X11R4 fonts and colors, a built-in BDF font compiler, and
built-in standard colormaps.
To connect your Macintosh to a network of machines capable of
running X-Windows clients, MacX uses MacTCP. For the best
performance, you will want to access this network through
LocalTalk or normal Ethernet. However, it is also possible
to make the connection over a high-speed modem and use MacX
to run X-Windows clients on remote machines; you will need
a SLIP LAP module for MacTCP to do this --- see [6.2] for the
details.
MacX can be purchased from official Apple retailers, such as
most university campus stores, for about $300 (less if you
qualify for an educational discount). MacX is also bundled
with A/UX 3.0.x.
For information regarding using MacX with A/UX, see the FAQ
for comp.unix.aux and/or ask questions in that newsgroup,
and/or investigate wuarchive.wustl.edu:/systems/aux/X11R5.
You _can_ run X11R5 directly under A/UX 3.0.x, which provides
significantly better performance.
The FAQ for comp.windows.x also describes another product,
eXodus, as follows:
eXodus from White Pine Software (603-886-9050) runs on any
Mac with at least 1MB of memory and runs the X server within
a standard Macintosh window. Version 5.0.x [10/94] supports
intermixing of X and Mac windows and the ADSP protocol. The
version supports the SHAPE extension and includes DECwindows
support.
eXodus supports X11R5 starting with version 5.0.
Another X server available for the Macintosh is XoftWare for
Macintosh, from AGE Logic. The company describes the product as
follows:
"XoftWare for Macintosh is AGE's enhanced X server software for the Apple
native Power Macintosh and 68K Macintosh platforms. Based upon Apple's
field-proven MacX(TM) server implementation and X11R5 server technology,
XoftWare for Macintosh offers many unique features that facilitate
Macintosh-to-UNIX connectivity. An intuitive single-button installation
utility, full support for accelerated Power Macintosh operation and System 7
compliance, support for enhanced login connectivity and Balloon Help are
just some of the features of AGE's advanced Macintosh-to-UNIX connectivity
solution.
"XoftWare for Macintosh is accelerated for the Power Macintosh and provides
native support for the Motorola 601 PowerPC microprocessor in addition to
full support for the 68030/68040 microprocessor family. Fully X11R5
compliant, XoftWare for Macintosh also takes advantage of the latest in X
server technology. Key features include XDMCP support, rexec and rsh remote
login options, and a single button installation. XoftWare for Macintosh is
System 7.5 compliant and utilizes the Macintosh local window manager to
maintain the Macintosh desktop look and feel. Support is also provided for
remote window managers such as mwm, olwm, and twm."
Finally, Tenon Intersystems includes its own X server with its
MachTen UNIX operating system for the Macintosh.
[6.2] How can I run MacX over a modem? Is it feasible?
------------------------------------------------------
Now that several SLIP LAP modules for MacTCP are available,
it is possible to run MacX over a modem. You are advised that
performance will be significantly poorer than you may be
expecting, especially if you are not using a high-speed modem
(eg: 9600 bps or higher with compression and/or error-
detection). With high-speed modems, using MacX to bring up
xterms and other text-oriented clients is usable; however,
any sort of graphics-intensive program (eg: xdvi) is going
to require some patience (but should be bearable).
Thus, in addition to MacX, to be able run MacX over a modem
you need:
1. A modem. A high-speed modem with v.32bis and v.42bis
is *STRONGLY* recommended.
2. A terminal-server at your site that offers dial-up
SLIP or PPP connections. You'll have to ask your
site or system administrator about this one.
3. A SLIP (or CSLIP) or PPP LAP module for MacTCP.
See [5.5] for details on such products.
If you are specifically interested in just having multiple
connections to a UNIX box that you connect to over a modem,
other options include using a Telnet program with SLIP (see
[5.3]), or MacLayers or UW [which do not need SLIP] (see [6.3],
[6.4]).
[6.3] What is MacLayers and what do I need to use it?
-----------------------------------------------------
MacLayers allows you to logon to a UNIX host and open more than
one window over a single (serial) connection. Each window
can correspond to a (login) shell or program running on your
choice of host(s). Up to seven full-screen resizable VT-100
windows are allowed.
In addition, MacLayers provides a primitive (but useful
anyway) mechanism to download binary files "in the background",
allowing you to work in other windows while you download.
No upload facility (except for text pasting) is provided.
At this time, MacLayers does not support the CTB. However,
it is freely distributable (but may not be sold).
MacLayers requires:
1. A UNIX host which supports sockets.
2. A Macintosh with 128 KB ROMs or larger.
MacLayers does not work with the old 64 KB ROM
machines. (You need a MacPlus or better).
MacLayers comes in two parts: a program you run on your
Macintosh and a set of C source files that you compile
on your UNIX host (a Makefile is provided). When you login
to your host while running MacLayers on your Macintosh, you
simply run one of the UNIX-side programs to start up the
windowing system (similar to running a windowing-environment
like X-Windows at the console, except that everything is
character based -- no graphics).
MacLayers is currently at version 1.30. The author is working
hard to improve MacLayers; current plans include better terminal
emulation, faster downloading, uploading, and more!
Please send all electronic correspondence regarding MacLayers
to the address layers@sapphire.cse.ucsc.edu. The latest
version of MacLayers is available via anonymous FTP at
ftp://sapphire.cse.ucsc.edu/pub/MacLayers/. You can find
the MacLayers WWW home page at
http://sapphire.cse.ucsc.edu/MacLayers/,
You are STRONGLY encouraged to upgrade to the latest version.
The most common response to requests for features and bug
reports is: "Get the latest version from rascal."
[6.4] What are UW and MultiSession? Are there other programs like MacLayers?
----------------------------------------------------------------------------
* Screen, a GNU product, can be found at various sites including
ftp://prep.ai.mit.edu/pub/gnu/screen-3.6.1.tar.gz.
From the man page:
Screen is a full-screen window manager that multiplexes a
physical terminal between several processes (typically
interactive shells). Each virtual terminal provides the
functions of a DEC VT100 terminal and, in addition, several
control functions from the ANSI X3.64 (ISO 6429) and ISO
2022 standards (e.g. insert/delete line and support for
multiple character sets). There is a scrollback history buffer for
each virtual terminal and a copy-and-paste mechanism that allows
moving text regions between windows.
* UW (short for UNIX Windows) is a program similar in style and
intent to MacLayers (see [6.3]) --- that is, it provides a
multi-window interface to a UNIX hosts. UW has been around a
lot longer than MacLayers but, as far as I know, hasn't been
updated in quite a long time. It offers most of the same
features as MacLayers, but no facility for downloading
is provided. UW does have the advantage of working with the
older 64 KB ROM machines, but in general, MacLayers is the
superior program.
* MultiSession is a recently released program with similar goals.
It includes error-correction in its Macintosh-to-UNIX protocol,
but this makes it quite sluggish. As of this writing (6/93),
the UNIX side of MultiSession runs properly only under ULTRIX.
For more information on MultiSession, please see its documentation
or contact the author; please do not send e-mail to the editor.
MultiSession's author is Thomas R. Lawrence (tomlaw@world.std.com).
[6.5] Is there a UNIX program that will convert between BinHex and MacBinary?
-----------------------------------------------------------------------------
Yes, there are at least two that will handle BinHex 4.0, MacBinary,
and other conversions. macutil and mcvert are distributed as
UNIX shar archvies and can be found in the unix directory at
InfoMac sites. Source code is included (of course) so you will
need a C compiler to build the programs:
* macutil
macutil is a collection of utilities for manipulating Macintosh
files in MacBinary [see 2.2] or BinHex [see 2.3] format, or over
AppleDouble, AUFS, or CAP servers.
As of (8/92), macutil includes three programs:
o hexbin - a program to convert BinHex 4.0 to MacBinary;
it also converts uuencode (and UULite) files to their
native binary format; support for .dl, .hex, and .hcx
formats (all predecessors of BinHex 4.0) also exists
o macsave - a MacBinary filter program to convert
between various MacBinary representations, including
a single .bin file, three separate .data, .rsrc, .info
files, and AUFS format. macsave also allows one to
"peek" inside MacBinary files
o macunpack - a program to unpack PackIt, StuffIt,
Diamond, Compactor/Compact Pro, most StuffIt Classic
and StuffIt Deluxe, DiskDoubler, Zoom and LHarc/MacLHa
archives.
It also decodes BinHex 5.0, MacBinary, uuencode, and
UNIX compress (ie: .Z suffix) files (as well as variants
of compress implemented by various Macintosh compress
programs).
Support for password protected and/or multi-segment
archives of various types is minimal or non-existent.
The various authors of the macutil utilities are too numerous
to list here; consult the README files that come with the package
for the details.
* mcvert
mcvert allows you to convert BinHex files to MacBinary files
and vice versa. In addition, you can create MacBinary files
with empty resource forks from normal files, as well as perform
other transformations. mcvert can also decode PackIt
archives.
mcvert was originally written in 1987 by Doug Moore, but is
now maintained by Joseph Skudlarek, jskudlarek@std.mentorg.com,
who has fixed added many new features and made mcvert easier
to use. The latest version of mcvert is available at InfoMac
sites.
* xbin
xbin is an old program, similar to a primitive version of mcvert.
It converts BinHex files into a set of three files which model
the data, resource, and info forks of a Macintosh file; recall
that all of this information is contained in a single MacBinary
file (see [2.2]). Unless you have software that can reconstruct
a MacBinary file from these three separate files (mcvert will
do this), xbin will be pretty useless.
xbin is pretty dead on UNIX platforms, but VMS folk continue to
use it because, unlike mcvert of the macutil pacakge, xbin
compiles under VMS.
[6.6] How can I create LaserWriter PostScript printer files and print them
--------------------------------------------------------------------------
on a PostScript printer connected to a UNIX network?
If you are running System 7.x or later, make sure you using
the LaserWriter 8.0 driver set (or something more recent,
such as 8.1.1). You can FTP these Extensions from Apple at
ftp.support.apple.com. Select Print from your application and
check the option entitled 'Disk File' or 'Print to Disk'.
Then click on Options and configure things to create a minimal
PostScript file by unchecking all boxes. Do not include
any extra fonts. Now, "print" the file.
If you are running System 7, you will be prompted to select
the destination folder and name for the PostScript file.
Otherwise, it will be named "PostScript' (or 'PostScript#'
where '#' is a digit) and placed either in the System folder,
the application's current folder, or the root folder on the
startup disk. You may rename the file.
Upload (or otherwise transfer) the PostScript file to your
UNIX system, treating it as a text file, unless you are
including graphics or fonts in your output (in which case you
should be safe and take the extra steps and treat the file as
an eight-bit binary file).
Note: If you are a pre-System 7 user or cannot upgrade to the
latest LaserWriter drivers, you are encouraged to read the file
tips/generating-postscript at InfoMac archives. Also check
out the program 'Trimmer'.
Note: If you are trying (vainly) to use Macintosh PostScript
files as figures using the psfig macro under Tex or LaTeX,
get the mactotex package from the University of Michigan's
archive site in util/unix. This utility makes importing
Macintosh PostScript files into (La)TeX painless; it also
includes a useful 'cleanps' utility, that strips Macintosh
PostScript files of unneeded parts.
If the PostScript printer is connected to a Macintosh, you can
use a shareware product such as lpDaemon, or a commercial product
such as Wollongong's "LPR Server," to turn that Mac into a print
server which will accept PostScript files from any TCP/IP host
on the network using the standard LPR protocol.
[6.7] How can I print over the network to a QuickDraw printer which
-------------------------------------------------------------------
doesn't support PostScript?
Currently the only product which fills this need is the PathWay Print
Redirector from The Wollongong Group. TWG provided the following
information about that product:
PathWay Print Redirector is the first QuickDraw GX based printing
software which provides transparent access to any LPR enabled printer
or a printer connected to a TCP/IP host. It features an intuitive GUI
where user authentication and printer setup are done through the Chooser.
Users may browse available print servers and iconize them on the desktop.
Printing can be accomplished by simply dragging-and-dropping files to the
desktop printer icon, or by printing from within the application.
Some of the salient features of PathWay Print Redirector include:
- First QuickDraw GX (TM) savvy printing software that supports
NFS and LPR protocols
- Intuitive GUI to browse, configure, and iconize remote network
printers on the desktop
- Drag&Drop documents to the virtual printer icon representing
remote network printer
- Print directly from Macintosh applications to remote printers
- Display and print documents without the application that created
the document
- View local print queue by double-clicking the printer icon
- Ability to suspend a specific print job or the entire print queue
- Ability to manage both local and remote print queues from the
desktop
- Provides network security and access privileges through PCNFSD
- Includes Apple's QuickDraw GX and MacTCP
[6.8] What is the Columbia AppleTalk Package (CAP)?
---------------------------------------------------
The Columbia AppleTalk Package allows supported UNIX machines to speak
AppleTalk, the built-in networking language every Macintosh running
the MacOS understands. CAP provides an AppleShare 2.0 compatible file
server (aufs) for sharing UNIX disks with Macintosh computers, a
LaserWriter spooler (lwsrv) for spooling Macintosh print-jobs and
a printing program (papif) for printing Macintosh files on Ethernet-
accessible LaserPrinters. Many other contributed programs are also
available. Using CAP, UNIX disks and printers can be made accessible
via the Chooser.
CAP is free and in common use wherever large AppleTalk and UNIX
networks converge. For more information, consult the documentation at
one of the following FTP sites:
rutgers.edu src/{cap60.tar.Z,cap60.patches/*}
munnari.oz.au mac/{cap60.tar.Z,cap.patches/*}
gatekeeper.dec.com pub/net/appletalk/cap/{cap60.tar.Z,cap.patches/*}
ftp.kuis.kyoto-u.ac.jp net/cap/{cap60.tar.Z,cap60.patches/*.Z}
src.doc.ic.ac.uk mac/multigate/{cap60.tar.Z,cap.patches/*}
An alternative to CAP that offers higher performance but is not currently
compatible with as many UNIX platforms is netatalk, available via FTP
from terminator.rs.itd.umich.edu.
Also, the IPTalk ADEV, written at the University of Melbourne (where ARNS
and CAP are both maintained), allows a Mac to use IPTalk to communicate
directly with CAP servers which don't support EtherTalk.
[6.9] How can I use the UNIX NFS file sharing protocol on my Mac?
-----------------------------------------------------------------
NFS, the Network File System, is the file sharing protocol used by many
UNIX workstations. You can access files stored on UNIX file servers
which are running an NFS server by using an NFS client on your Mac.
You must be connected to an IP network and be using MacTCP to use NFS on
your Mac. Two Mac NFS client programs (both are commercial products; no
shareware Mac NFS client currently exists) are
* NFS/Share(TM) from Intercon Software
* Simple to use -- files from the remote systems take on the
format of the Mac documents you always use. There are no new
operating procedures or software systems to learn. Certain
text files, such as UNIX, are accessible from any Macintosh
editor or word processor.
* Macintosh resident -- Once you have the physical link to the
network and NFS/Share, you need nothing other than access to
NFS servers on the network. NFS/Share works with Macintosh
computers and is completely System 7.0 compatible
* Access multiple remote machine easily -- Just go through Apple's
Chooser and you are there. A list of available servers on remote
systems appears in a pop-up window. You can access remote
machines at the same time, and, just like your hard drive,
they appear as icons on your dektop
* Apple standard -- NFS/Share uses Apple's defined standards
(AppleSingle or AppleDouble) for representing files for foreign
file systems
* Simultaneous access -- Multiple users can easily access the
same infomation at the same time without the need for different
mounting points.
* Security maintained -- User authentication done through Sun
Microsystem's NIS (Yellow Pages), PCNFSD, or BWNFSD. Each user
is presented with lists of access or mounting points automatically.
* PathWay Client NFS from The Wollongong Group
* High-performance NFS client designed for Macintosh computers
using either System 6 or System 7.
* Utilizing the NFS protocol, PathWay Client NFS users can share
files and use applications that reside on local and/or remote
systems that have NFS servers.
* Easily accessed through the chooser to mount NFS server volumes,
just like AppleShare.
* Simple installation via installer script
* Supports symbolic links
* Support for browsing NFS servers and remote printers
* Supports PCNFSD 2.0 for user authentication, and multiple GIDs
are supported
* Supports LOCKD and BWNFSD for file sharing and record locking
* User-definable file permissions
* Ability to mount multiple NFS volumes at boot time
* Displays RPC information such as mount points, server daemons, etc.
* Ability to function as a print server
* Includes MacTCP and SNMP agent
* Supports non-default authenatication daemons
[Note: The above information was taken directly from sales information
provided by the two companies.]
================================================================================
[7] Sending and receiving Mail and Usenet News with your Macintosh
==================================================================
[7.1] How can I send/receive Internet mail with my Macintosh?
-------------------------------------------------------------
There are a variety of ways to do this depending primarily
on how you connect your Macintosh to the rest of the world.
The most popular and practical methods are summarized below:
Note: Methods of sending and receiving e-mail that are specific
to A/UX are not discussed; see the FAQ for comp.unix.aux.
* UUCP
Perhaps the most practical way to interact with Usenet for most
is to use UUCP (Unix-to-Unix-Copy). UUCP is a protocol originally
intended to be used to transfer files between Unix machines over
telephone lines. Various UUCP programs exist for the Macintosh,
from freeware to shareware to payware. In addition to the UUCP
software, you must find a host machine connected to the Internet
(or equivalent) that is willing to send and receive your e-mail
(and news, if you wish [see 7.2]). There are commercial
services that provide this capability in various regions of
the country; check the newsgroup alt.bbs.internet for more
information. Once you have identified and arranged to receive
and send e-mail from such a service, you need to register your
site with a unique name in the UUCP maps.
-> Mac/gnuucp is a port of the GNU UUCP sources to the Macintosh.
Sources are included. The interface uses the standard Think C
command-line substitute. A Hypercard mail reader is provided.
Usable, but not recommended if you intend on transfering a lot
of files.
-> UUPC 3.0 is a substantially better freeware implementation of
the UUCP protocol for the Macintosh. UUPC 3.0 includes support
for various flavors of UUCP that provide better performance
with high-speed error-correcting modems. Full source code
is provided. UUPC 3.0 was implemented by a coalition of
programmers led by Dave Platt. Thanks!
-> uAccess, a payware product (about $300) from Ice
Engineering supports the CTB and can be used to send and
receive both e-mail and news postings via a UUCP link.
See [7.2] for more information.
* MacTCP: SMTP, POP
SMTP (Simple-Mail-Transfer-Protocol) and POP (Post-Office-
Protocol) are two protocols for transfering electronic mail
between machines that have a TCP/IP interface or equivalent.
Usually, on the Macintosh, such an interface is provided via
MacTCP and/or the Communications Toolbox.
-> Eudora is perhaps the best written and most popular e-mail
program available for the Macintosh. Eudora is a complete and
versatile e-mail package which can send e-mail via SMTP (either
through the CTB or a serial connection) and receive e-mail via
a POP server. It can even be used with UUPC 3.0 (as a mail
reader and message generator, not a transport agent). Eudora
can also be used to transfer arbitrary Macintosh files between
computers through its BinHex 4.0 attachment features. Many
accolades go to the author, Steve Dorner. Free and commercial
versions of Eudora exist: (1/94)
Eudora 1.3.1 (free) -- last version to work under System 6 & 7
Eudora 1.51 (free) -- System 7 only; expanded feature set
Eudora 2.1 (pay) --- commercial version; even more features
You can FTP the free versions of Eudora from ftp.qualcomm.com
in mac/eudora. Please send all e-mail inquiries about Eudora
to eudora-info@qualcomm.com . Qualcomm has said it will continue
to release new versions.
-> MailShare is a Macintosh-based SMTP and POP server. MailShare also
supports a Password server, and includes NotifyMail support, both of
which can be taken advantage of by Eudora, a Macintosh and Windows mail
client.
The most current version of MailShare is 1.0fc5. It is available at
ftp://ftp.winternet.com/users/carl/MailShare-10fc5.hqx. You can find the
MailShare home page at http://www.winternet.com/~carl/mailshare/mailshare.html
AutoShare, an extension to MailShare written by Mikael Hansen which provides
listserv-like capabilities to the package, is currently in a non-public
development release. According to the author,
"AutoShare is a MailShare utility that lets you create a subject based
auto-answering service; Binhex enclosures accompanying automated responses
are optional. You may use it as a vacation service as well. AutoShare has
also been extended to function as a simple listserver; listserver commands
are SUBscribe, UNSUBscribe, LIST, REVIEW, SET (conceal, noconceal, digest,
nodigest), INDEX, GET, WHICH, and RELEASE. Furthermore, an
(outgoing)UUCP-MailShare gateway is included."
Further information is available at the AutoShare home page.
http://www.kb.bib.dk/autoshare/autoshare.html
-> LeeMail is a shareware ($25) MacTCP-based SMTP and POP3 mailer for
the Macintosh. LeeMail allows you to send and receive Internet
mail directly from your Macintosh --- if you have a fixed IP
address (manual addressing). Otherwise, if your Macintosh uses
dynamic addressing to determine its IP address, you can use
LeeMail to send mail from your Macintosh but should use a
different Reply-To address. LeeMail supports various enclosures.
Author: Lee Fyock <laf@chs.cusd.claremont.edu>
-> TCP/Connect II, from Intercon Systems, includes support for
both SMTP and POP based e-mail.
* Other:
-> Fernmail, a shareware program ($20), can be used as a stand-
alone mailer program to read and compose e-mail messages. It can
also be used to send e-mail between different users of the same
Macintosh but has no built-in facility to transfer messages
between machines. It is most useful as a front-end for UUCP
mailers that lack a sophisticated mail management program.
Author: Dave Platt <dplatt@snulbug.mtview.ca.us>
[7.2] How can I read/post Usenet news with my Macintosh?
--------------------------------------------------------
Again, the various options depend primarily on how your
Macintosh is connected to Usenet. The various ways to
connect your Macintosh to outside networks are summarized
elsewhere in this FAQ. What follows is a brief description of
the more popular software packages, according to connection
method.
Note: Methods of sending and receiving news that are specific
to A/UX are not discussed; see comp.unix.aux instead.
* UUCP
-> uAccess, a commercial product (about $300) from Ice
Engineering (and the product from which uATerm and Termy were
derived) is a well-designed product that works well enough to
allow you to use your Macintosh as a Usenet node (if you have
enough disk space). uAccess supports the CTB and comes with a
terminal emulator. It was reviewed in the July, 1992 issue of
_UnixWorld_.
-> rnMac, a shareware program ($25) written by Roy Wood
<rrwood@canrem.com>, is a reasonably spiffy offline newsreader.
The original intention was for rnMac to work in conjunction with
UUPC and ToadNews (by John Mah <jpmah@descartes.uwaterloo.ca>)
to allow you to set up a uucp-based Usenet newsfeed on a Mac.
rnMac is quite stable and full-featured, and even does a passable
job as a mailer (no match for Eudora, FernMail, etc.). rnMac,
ToadNews, UUPC are each available from archive sites such
as sumex and umich.
-> TheNews is a shareware ($25) MacTCP-based NNTP news reader.
This program also supports UUCP transfer of news, and allows
responding to articles via a local SMTP server as well.
Author: Bill Cramer <70322.3412@compuserve.com>
* MacTCP - NNTP
Most (if not all) MacTCP-based newsreaders for the Macintosh
will require access to a NNTP news server. NNTP (Net News
Transfer Protocol) is a protocol used to transfer articles
between a central news server and many client machines over
TCP/IP or a serial link.
-> NewsWatcher is a free MacTCP-based NNTP news client. It
supports a graphical "point and click" interface for browsing
and reading news. The program was featured in Apple's technical
"d e v e l o p" magazine (#6) with source; you can also FTP the
source from ftp.support.apple.com. The application itself is
available at other archives.
Development versions of NewsWatcher are generally made available
for anonymous FTP from ftp.acns.nwu.edu in the directory
pub/newswatcher.
Contact: send e-mail to <newswatcher@phil.ruu.nl>
-> Nuntius is a thread-based, MacTCP-based NNTP news reader with
a graphical Finder-like user interface. It is actively supported
by its author. One nice feature of Nuntius is its ability to
automatically extract binaries from selected threads. Nuntius
is designed to be used with Eudora as its editor and mailer.
Author: Peter Speck
More information: there is a mailing list supporting the the Nuntius
program. Send e-mail to <nuntius-l@cornell.edu> to distribute
a message to the list.
-> InterNews is described as "a Macintosh interface to the world
of Usenet news". It is a relatively new but well-designed MacTCP-based
NNTP client for the Macintosh. Subscriptions, newsgroups, and articles
are organized and selectable via resizable and configurable panes.
InterNews is free to users of educational and non-profit organizations;
it is available for anonymous FTP at ftp.dartmouth.edu:/pub/mac.
Commercial and government users are asked to purchase a license.
-> TheNews is a shareware ($25) MacTCP-based NNTP news reader.
This program also supports UUCP transfer of news, and allows
responding to articles via a local SMTP server as well.
Author: Bill Cramer <70322.3412@compuserve.com>
-> TCP/Connect II, from Intercon Systems, includes an NNTP based
news reader, as well as e-mail (and other) facilities.
-> VersaTerm-Link includes a NNTP based news reader, as well as
e-mail facilities.
* Serial - NNTP
--> NetFeed is a NNTP newsreader designed to communicate with
a NNTP server via modem. It includes an article reader and
a simple scripting language to facilitate dialing the modem.
NetFeed is shareware, but the authors seem to only ask for a
postcard if you use their software.
Authors: Bill Burns <WDBURNS@MTUS5.bitnet>
Brad Boyer <BRBOYER@MTUS5.bitnet>
================================================================================
[8] Miscellaneous
=================
[8.1] I don't have FTP --- How can I access the Macintosh FTP archives
----------------------------------------------------------------------
through e-mail?
First, look in the Appendix of this FAQ. Descriptions on how
to access mailservers that mirror the InfoMac archives are
provided there. Also, the University of Michigan maintains
an e-mail server for its Macintosh archive; send a message
to mac@mac.archive.umich.edu with the command "help" in
the message body for details.
If you have Gopher access, note that the InfoMac archives at
sumex-aim.stanford.edu are accessible via Gopher. If your
Macintosh is connected to the Internet via MacTCP, for example,
you can use one of the many Macintosh Gopher clients to
access InfoMac.
If you have AFS (Andrew File System) access, you can access
the Macintosh archive at the University of Michigan via your
UNIX file system: cd /afs/umich.edu/group/itd/archive/mac .
You may have to ask your AFS/system adminisrator to add
umich.edu to the list of mounted AFS sites, however.
If you have WWW access, you can point your WWW browser to
gopher://gopher.lcs.mit.edu/h0/HyperActive
For more general help on accessing FTP sites through e-mail,
send e-mail to mail-server@rtfm.mit.edu and include a line
containing "send usenet/news.answers/finding-sources" in the
message body. You will be e-mailed instructions on how to use
FTP sites via e-mail.
[8.2] What aids are available for programmers wishing to write TCP/IP
applications for the Macintosh?
--------------------------------------------------------------------------
* PathWay API Developer's Tool Kit Macintosh from The Wollongong
Group provides:
* BSD 4.3 Sockets library
* Stream (TCP) and datagram (UDP) socket types
* Blocking and nonblocking socket modes
* Include files and sample programs for Apple MPW 3.2
* PathWay API Programming Guide
* Works on System 6.0.x, 7.0, and 7.1
[8.3] I have a FAX machine and a FAX modem. How can I use these devices
together to emulate a scanner and a printer?
------------------------------------------------------------------------
It is often possible to simply connect your FAX modem to your
FAX machine using a regular telephone cable. You can then print
to your FAX machine by sending a document to your FAX modem (then
through the cable to your FAX machine, to be printed). Analogously,
you can "send" a FAX from your FAX machine to your computer's FAX
modem and thus emulate a scanner (the FAX image will be read into
your computer by your FAX modem software).
This phone cable connection does not always work, however. For
these cases, P.E.P. Products, Inc., offers faxScan/faxPrinter,
a Macintosh and Windows-compatible product which allows you
to connect your FAX modem to your FAX machine and thus gain the
ability to print from your computer to the FAX machine and
scan into your computer from the FAX machine, as described
above. This device is pocket-sized, 1.05 ounces, and powered
by a 9 volt battery. According to the company's sales information,
"The faxScan/faxPrinter device stabilizes line voltages
on both sides, allowing any combination of FAX modem and FAX machine
to work together. This product is useful if you travel and want to
print or scan using any fax machine."
================================================================================
Appendix
========
[A] List of Common Abbreviations
--------------------------------
Abbrev-
iation Description
------- ------------------------------------------------------
A/UX Apple Unix
ADB Apple Desktop Bus
AFE Apple File Exchange
ARA Apple Remote Access (was AppleTalk Remote Access)
bps bits per second
CSLIP Compressed SLIP
csmc comp.sys.mac.comm
CTB Communications Tool Box
CTS Clear-To-Send
DSR Data-Set-Ready
DTR Data-Terminal-Ready
FTP File Transfer Protocol
IP Internet Protocol
LAP Link Acess Protocol
MNP Microcom Networking Protocol
NNTP Net News Transfer Protocol
PPP Point-to-Point Protocol
RTS Request-To-Send
SID Sound Input Device
SLIP Serial Line Internet Protocol; also seen as SLIP
TCP Transmission Control Protocol
uw Unix Windows
[B] List of Macintosh archive sites available through the Internet
------------------------------------------------------------------
All shareware or freeware programs described in this FAQ are available
from one of the many archives that mirror the InfoMac archives at sumex
and at other Macintosh FTP sites described below.
Of course, since almost all files are distributed in BinHex format,
the first program you need to get hold of is "BinHex 4.0" or better --
one of the programs described in [2.3] that has the capability to
decode BinHex files. If you have FTP access, try to FTP the file
info-mac/util/binhex4.bin from sumex-aim.stanford.edu with 'binary'
mode set (issue the command 'binary' to the FTP server). This file
is a MacBinary version of BinHex 4.0. If you don't have a binary-
capable FTP, or if you forget to use binary, you will get a corrupted
file when you transfer the file to your Mac. Alternatively, you can
FTP a MacBinary version of StuffitExpander from wuarchive.wustl.edu
in /systems/mac/info-mac/util as the binary file stuffit-expander-303.bin.
If you don't have FTP access or binary FTP doesn't seem to work for you,
try to friend who has BinHex 4.0 (or equivalent) on a disk that you can
copy. Or, if you have a Pascal compiler handy, you can download the
Pascal source from sumex and compile it. But your best bet is to ask
around.
Unless otherwise indicated, the following FTP sites are all anonymous
FTP sites available through the Internet. Logon as "anonymous" or "ftp"
and give your e-mail address as the password. Remember that the use of
anonymous FTP at these sites is a privelege, not a right, so please act
accordingly. Type 'ls' to get a directory listing. Use the command 'cd'
followed by a directory name to move to a specific directory. USe the
command 'cd ..' to move back "up" to the previous directory.
Issue the command 'binary' to change to FTP BINARY mode. Give the command
'get' followed by a filename to retrieve a specific file.
Sites are grouped by geographical location. North American users are
strongly encouraged to use the North American sites. Practically
everything found on other continents can also be found somewhere in
North America. Similarly, non-North American users are advised to check
out their local sites first. ftp.support.apple.com is the notable exception.
If you know one info-mac archive site, you can retrieve a list of all
the info-mac archive mirrors by accessing URL
ftp://<any_info-mac_site>/info-mac/help/mirror-list.txt>
NORTH AMERICA:
** ftp.support.apple.com **
This FTP site is maintained by Apple. You can FTP System 7, TuneUp,
various Developer Technical Support items (including all the Tech
Notes), QuickTime, and much more. You will need the Apple DiskCopy
program (available online) to make floppy-disk versions of the disk
images.
** mac.archive.umich.edu ** (141.211.32.2)
University of Michigan's Macintosh Public Domain and Shareware Archive.
All files are in the mac directory (mac.bin is a directory useful only
to local University of Michigan users). Has lots of Macintosh files that
don't seem to be available anywhere else (including many that are not
at sumex-aim.stanford.edu). Announcements of recent additions to the
archives are routinely seen in comp.sys.mac.digest. Read the file
'/mac/00help/submissions.txt' for details on submitting. The archive
is accessible via AFS (the Andrew File System) which is by far the
best way to access it; see [8.1].
** microlib.cc.utexas.edu **
The University of Texas Computation Center maintains a large and useful
Macintosh archive in microlib/mac (Archives for other personal computers
are also available here). Submissions can be e-mailed (in BinHex form)
to macgifts@mac.archive.umich.edu (which are then rebroadcasted
elsewhere; this is the easiest way to distribute public-domain or
shareware stuff throughout the Internet).
** sumex-aim.stanford.edu ** (36.44.0.6)
Official home of the Info-Mac archives. This site is heavily used and has
anonymous FTP connections limited during local working hours, so you are
STRONGLY encouraged to use one of the many sites which mirror the sumex
archives (such as mac.archive.umich.edu or wuarchive.wustl.edu). All
Macintosh files are stored in the directory info-mac in a tree
structure by generic file type. Announcements of recent additions are
posted (daily) to comp.sys.mac.digest. You should read the file in the
help subdirectory called 'posting-guidelines.txt' for details on
submitting files to the archive. This site is also accesible via Gopher.
** wuarchive.wustl.edu ** (128.252.135.4)
Washington University maintains a mirror archive of sumex-aim and also
mac.archive.umich.edu (among others). Look in mirrors/info-mac and
mirrors/archive.umich.edu respectively. This site is also useful for
other reasons and can be mounted via NFS (see the README files in the
top level).
If you don't have FTP access, you can access the sumex-aim InfoMac
archives by using the LISTSERVer at Rice University in Houston, TX.
For example, to retrieve the file util/cpt-expand-10.hqx, send a message
containing the line "$macarch get UTIL/CPT-EXPAND-10.HQX" to
listserv@ricevm1.rice.edu. UNIX users may also find the following script
useful:
#!/bin/csh -f
# macarch.get
if test $# -ne 1
then
echo Usage: $0 archive-name-of-file-to-retrieve
exit 1
fi
echo \$macarch GET $1 | mail LISTSERV@ricevm1.rice.edu
The files HELP/ALL-FILES.TXT, HELP/ACCESSING-FILES.TXT, and other
files in the HELP hierarchy are useful files to try retrieving
initially.
EUROPE:
** ftp.funet.fi ** (128.214.6.100)
The Finnish University and Research network (FUNET) archive site.
Macintosh files are in pub/mac. Read the README file in the top level,
especially if you are FTP-ing "long distance".
** nic.switch.ch ** (130.59.1.40)
The Swiss Academic and Research Network (SWITCH) maintains an info-mac
mirror on nic.switch.ch. Files are in the directory /mirror/info-mac
and are updated daily.
** src.doc.ic.ac.uk ** (146.169.2.1)
Archive site maintained by UKUUG Software Distribution Service,
Department of Computing, Imperial College, London, UK. Macintosh
files are in directory packages/mac. Mirrors of sumex-aim.stanford.edu
and mac.archive.umich.edu are in mac/sumex and mac/umich respectively.
Some files are compressed using Unix compress (.Z); see the README
file.
** irisa.irisa.fr ** (131.254.254.3)
Archive site maintained by Institut de Recherche en Informatique et
Systemes Aleatoires in Rennes, Brittany, France. This site maintains an
archive of various comp.binaries.* group, including comp.binaries.mac.
Files are in News/comp.binaries.mac. Warning: Files in this directory
are numbered and numerous so avoid asking for a directory listing;
that is, don't type 'ls' or 'dir'. Rather, change to this directory
and download the file 'index' which maps the "Subject:" line to
a number which you can then 'get'.
If you don't have FTP access, you can access the InfoMac archives
by sending e-mail to the mirror archive kept on fileserv@irlearn.ucd.ie.
Files must be requested by their (14 digit) number, so first send
a message containing only the line "get macfile listing" for a full
index, or ask for the most recent additions by sending "index newmac".
AUSTRALIA:
** archie.au ** (139.130.4.6)
AARNet Archive Server, Melbourne, Australia. Macintosh files are
in micros/mac. This site also mirrors sumex-aim.stanford.edu (look in
micros/mac/infomac) and mac.archive.umich.edu (look in micros/mac/umich).
JAPAN:
** utsun.s.u-tokyo.ac.jp ** (133.11.11.11)
University of Tokyo archive site. Macintosh files are in pub/Mac.
This site also mirrors info-mac at sumex-aim.stanford.edu; check
the pub/Mac/info-mac directory.
[C] Vendor Information
----------------------
These vendors are either mentioned in this FAQ or provide products
relating to Macintosh networking. Neither the editor of this list
nor any of the contributors necessarily endorse any of the vendors
or their products. The following information is provided for your
convenience only.
Please bring any errors or additions to the attention of the editor.
Vendor Contact Methods:
--------------------------------------- --------------------------------
About Software Corporation [USA] (408) 725-4249
e-mail: diane@ascus.com
anonymous FTP at ftp.ascus.com
Advanced Software Concepts e-mail:
adv.soft@applelink.apple.com
anonymous FTP at 192.70.34.153
AGE Logic, Inc. [USA] (619) 455-8600
e-mail: sales@age.com (sales)
e-mail: support@age.com (support)
Alverson Software e-mail: davea@xetron.com
Apple Developers Association (APDA) [USA] (408) 974 4667
e-mail: APDA@applelink.apple.com
MacTCP orders and information:
[USA] (800) 282-2732
[USA] (408) 562-3971 {FAX}
[CANADA] (800) 637-0029
Asante e-mail: support@asante.com
AppleLink: asante.tech
Anonymous FTP at ftp.asante.com
Carnation Software [USA] (206) 333-4288
e-mail: richlove@netcom.com
HTML home page (ftp) at ftp.netcom.com
in /pub/carnation/HT.Carn.Home.html
Cayman Systems [USA] (800) 473 4776
e-mail: info@cayman.com
e-mail: sales@cayman.com
anonymous FTP at ftp.cayman.com
cc:Mail/Lotus Development [USA] (800) 448-2500
[Int'l] 011-44-784-455-445
e-mail: support@ccmail.com
Celestin Company [USA] (800) 835-5514
[USA] (206) 385-3767
[FAX] (207) 385-3586
AOL: Celestin
CompuServe: 71630,650
e-mail: celestin@pt.olympus.net
Compatible Systems [USA] (800) 356 0283
e-mail: support@compatible.com
anonymous FTP at ftp.compatible.com
Creative Solutions, Inc. [USA] (800) 367-8465
[USA] (301) 984-0262
[FAX] (301) 770-1675
AppleLink: CSI
CompuServe: 70240,504
eWorld: 'CSI Tech'
e-mail: 70240.504@compuserve.com
Dayna Communications [USA] (801) 269-7200
[USA] (801) 269-7363 (fax)
e-mail: sales@dayna.com (sales)
e-mail: support@dayna.com (support)
AppleLink: dayna
AppleLink: dayna.tech (customer service)
e-mail: dayna@tigger.jvnc.net
AOL: DAYNACOM
Farallon Computing [USA] (510) 814-5100
e-mail: farallon@farallon.com
Freesoft [USA] (412) 846-2700
Global Village [USA] (415) 390-8200
[USA] (800) 736-4821
[FAX] (415) 390-8282
e-mail: sales@globalvillag.com (sales)
e-mail: techsupport@globalvillag.com
WWW: http://www.globalvillag.com/
FTP: ftp://ftp.globalvillag.com/
America Online: GlobalVill
CompuServe: 75300,3473
Hayes [USA] (404) 441-1617
[CANADA] (519) 746-5000
[USA/CANADA] (800) US-HAYES {BBS}
[USA/CANADA] (404) HI-MODEM {BBS}
[UK] 081-848-1858
[UK] 081-569-1774 {BBS}
[HK] 852-887-1037
ICE Engineering, Inc. [USA] (313) 449-8288
e-mail: info@ice.com
e-mail: time@ice.com
InterCon Systems [USA] (800) 468-7266 (sales)
[USA] (703) 709-5500 (sales)
[USA] (703) 709-5520 (tech)
e-mail: sales@intercon.com
Mark/Space Softworks [USA] (800) 799-1718 (sales)
[USA] (510) 843-6485 (sales)
[USA] (408) 293-7299 (support)
[USA] (408) 293-7298 (fax)
[USA] (408) 293-7290 (bbs)
e-mail: mspace@netcom.com
eWorld: MARKSPACE1
CIS: 73244,3333
America Online: MARKSPACE
AppleLink: MARKSPACE
FTP: ftp://ftp.netcom.com/pub/ms/mspace
Mercury System, Inc. [USA] (310) 553-0881
[USA[ (310) 553-1291 (fax)
Pacer Software [USA] (619) 454-0565
e-mail: support@pacersoft.com
P.E.P. Products, Inc. e-mail: pep@borealis.com
QUALCOMM, Incorporated [USA] (800) 2-EUDORA
[USA] (619) 587-1121
e-mail: eudora-hotline@qualcomm.com
ftp: ftp.qualcomm.com [192.35.156.5]
Seaquest Software [USA] (503) 531-0252
[USA] (503) 629-8442 (fax)
e-mail: seaquest@netcom.com
AppleLink: D0937
America Online: Seaquest1
eWorld: Seaquest
Shiva [USA] (800) 458-3550
[USA] (617) 621-0190 {BBS}
e-mail: info@shiva.com
e-mail: sales@shiva.com
e-mail: support@shiva.com
anonymous FTP at shiva.com
Smartcom (Hayes) [USA] (404) 441-1617
[USA] (800) US-HAYES (BBS)
Software Ventures Corporation [USA] (510) 644-1325
e-mail: microphone@svcdudes.com
Sonic Systems [USA] (408) 736-1900
[USA] (800) 535-0725
e-mail: sales@sonicsys.com
Stalker Software [USA] (800) 262 4722 (voice)
[USA] (408) 370 3170 (fax)
[EUROPE] 49 221 442 138
StarNine Technologies [USA] (510) 649-4949
[USA] (510) 548-0393 (fax)
e-mail: info@starnine.com
Supra Corporation [USA] (800) 727-8772 main
[USA] (503) 967-2400 international
[USA] (503) 967-2492 tech support
[USA] (503) 967-2401 fax
[USA] (503) 967-0072 fax-back info
e-mail: tech_support@supra.com
Synergy Software [USA] (215) 779-0522
e-mail: maxwell@sales.synergy.com (sales)
e-mail: upgrade@synergy.com (upgrade info)
e-mail: synergy1@tech.abelbeck.com (tech
support)
Tenon Intersystems [USA] (800) 963-6983
[USA] (805) 963-6983
e-mail: sales@tenon.com (sales)
e-mail: support@tenon.com (support)
TriSoft (Hyde Park sales/support) [USA] (800) 531-5170
Webster Computer Corp. [AUSTRALIA] 61 3 764 1100
White Pine Software [USA] (603) 886-9050
The Wollongong Group, Inc. [USA except California] (800) 872-8649
[California only] (800) 962-8649
e-mail: sales@twg.com
Walker Richer & Quinn, Inc. [USA] (800) 872-2829 (sales)
[USA] (206) 217-7100 (sales)
[USA] (206) 216-2689 (sales FAX-back)
[USA] (206) 217-7000 (support)
[USA] (206) 216-2680 (support FAX-back)
[Europe] +31.70.375.11.00 (den Haag, Netherlands)
[Europe] +31.70.356.12.44 (FAX)
BBS: (206) 217-0145 or telnet to bbs.wrq.com
BBS: +31.70.356.27.25 (Europe)
e-mail: sales@wrq.com (sales)
e-mail: support@wrq.com (support)
ftp: ftp.wrq.com
www: http://www.wrq.com
AppleLink: WRQ.SUPPORT
CompuServe: GO WRQFORUM
ZyXEL [USA] (800) 255-4101
[USA] (714) 693-0808
[USA] (714) 693-0762 (BBS)
[USA] (714) 693-8811 (fax)
[CANADA] (416) 534-1508
[CANADA] (416) 534-1312
[D] Contributors
----------------
The editor of this FAQ would like to graciously thank all of the
following individuals who have contributed in some form or another
to the answers provided above, and to the many others not listed
who have nonetheless encouraged and corrected me along the way.
Dave Alverson (ZTerm, Powerbooks)
Steve Baumgarten (Versaterm)
Jack Brindle (BinHex, MacBinary)
Eric Behr (MacTCP)
Jim Browne (NCSA Telnet)
Josh Cole (Networking, MacTCP, AppleDouble)
Bill Coleman (Smartcom)
Celeste Dolan (Question [2.6])
Steve Dorner (Eudora, SLIP)
Don Gilbert (SLIP)
Tom Gewecke (European E-Mail, Archives)
Bruce Grubb (File compression/decompression charts)
Elliotte Rusty Harold (General, File Transfer Programs)
Patrick Hoepfner (SLIP v. PPP and various other tidbits)
Greg Kilcup (MacX, CSLIP, PPP)
Andy Y. A. Kuo (Networking)
Peter N. Lewis (General, FTPd)
Ward McFarland (Macintosh serial port speeds)
Bill MacGregor (MacTCP Name Resolution)
Leonard Rosenthol (General, StuffIt)
Richard Saint (MacPPP frequently asked questions)
Kevin Eric Saunders (Comet)
Eric P. Scott (General)
Jon L. Spear (General, Baud Etymology)
Irwin S. Tillman (IP over Local/EtherTalk, IP over ARA,
Ethernet/LocalTalk bridging)
Werner Uhrig (Macintosh Expert)
Rick Watson (MacSLIP)
================================================================================